• Login
  • Register

DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

SQL Server 2014 Restore failure

You are not authorized to post a reply.
Sort:


New Around Here


Posts:4
New Around Here

    I had this problem on a VPS with SQL 2014 Express. There was not enough security permission to a do a restore from the default backup directory: C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Backup (although backups worked fine)

    The error was: C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Backup Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists.

    Actually, you can follow these steps to change the authority:Log in to SSMS using Windows Authentication Navigate to Security->Logins Either double Click, or Right Click and select Properties on the user you're interested in . In the "Select a page" box, select "Server Roles" Make sure that the "sysadmin" role is selected Press Ok to save the change and close the dialog Exit SSMS Reopen SSMS and login as the User you wanted, and you should now have sufficient Privileges



    Veteran Member


    Posts:529
    Veteran Member

      if the database exists, membership of dbcreator role should be sufficient (https://docs.microsoft.com/en-us/sql/t-sql/statements/restore-statements-transact-sql?view=sql-server-2017)


      New Around Here


      Posts:2
      New Around Here

        One simple way is backup by using T-SQL

        Create a Full Database Backup using Transact- SQL or T-SQL to restore the database from .BAK file

        1. Type the BACKUP DATABASE statement which creates Full Database Backup using following specifications:

          RESTORE DATABASE AdventureWorks FROM DISK = 'C:\AdventureWorks.BAK'

          • Name of Database to backup
          • Place where to write the Full Database backup
          • The Syntax for full DB-backup is:


        New Around Here


        Posts:25
        New Around Here

          Hi, 

          Kindly make sure change the DB to an offline or single user to restore properly some time if it's in use the backup will not restore.

          3ART TechnologiesRegards,
          Rashid Imran Bilgrami

          3ART Technologies
          Experts in Analysis, Design & Development for DNN and SharePoint Solution
          http://www.3art.tech/


          New Around Here


          Posts:4
          New Around Here

            I have had no problem doing a db restore to a production SQL server by simply stopping the IIS service first. I also make sure the option to overwrite (replace) is set as part of the restore.
            Hope this helps.



            New Around Here


            Posts:4
            New Around Here

              If doing a restore to a different SQL Server (not the one backed up) e.g., restoring a staging SQL Server db to production SQL Server db or the other way the Login and dbUser GUIDs will not match. To correct that you will need to sync the user with the login by running the script:

              USE [database]
              GO
              EXEC sp_change_users_login 'update_one', '[loginname]', '[username]'
              GO 

              Generally the loginname and username will be the same.

              Hope this helps



              New Around Here


              Posts:1
              New Around Here

                Hi, 

                Kindly make sure change the DB to an offline or single user to restore properly some time if it's in use the backup will not restore.

                You are not authorized to post a reply.

                These Forums are dedicated to discussion of DNN Platform.

                For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

                1. If you have (suspected) security issues, please do not post them in the forums but send an email to [email protected]
                2. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
                3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
                4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
                5. No Flaming or Trolling.
                6. No Profanity, Racism, or Prejudice.
                7. Site Moderators have the final word on approving / removing a thread or post or comment.
                8. English language posting only, please.

                Would you like to help us?

                Awesome! Simply post in the forums using the link below and we'll get you started.

                Get Involved