Error 5170 microsoft sql server

error 5170 microsoft sql server

Error deploying deployment descriptor [C:\Program Open Microsoft SQL Server Management Studio, connect to the SQL Server hosting the Markvision. Error: CREATE DATABASE FAILED. Assume that my database file name is sprers.eu This mdf file was working fine till last week. I see the job failed with error in log: Message. Cannot create file 'E:\MSSQL\DATA\mydb. Error: , Severity: 16, State: 1. error 5170 microsoft sql server

Can recommend: Error 5170 microsoft sql server

Error 13 grub
Error 5170 microsoft sql server
Borland poscal error 8

Andrew Cushen&#;s Blog

The problem

I recently had, for the first time, to create a brand-new sprers.eu web application that made use of the built-in Membership/Roles functionality, using the default of SQL Server Express, NOT a full installation of SQL Server. I had previously wrestled with issues when upgrading an older application using Membership/Roles to sprers.euand blogged about it. However, this issue was specific to a brand-new sprers.eu application, albeit with VS SP1 and SQL Server SP1 installed.

All was well until I error 5170 microsoft sql server up the Web Site Administration tool and clicked the Security tab. I was suddenly greeted with the following error message:


There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager error 5170 microsoft sql server not being enabled. Click the button below to be redirected to a page where you can choose a new data store.

The following message may help in diagnosing the problem: An error occurred during the execution of the SQL file &#;sprers.eu&#. The SQL error number is and the SqlException message is: Cannot create file &#;C:\[Application_PATH\APP_DATA\ASPNETDB_sprers.eu&#; because it already exists. Change the file path or the file name, error 5170 microsoft sql server, and retry the operation. CREATE DATABASE failed. Some file names listed could not be created. Check related errors. Creating the ASPNETDB_[app GUID] database&#;


I checked the App_Data directory, and, sure enough, the ASPNETDB_sprers.eu file was there.

Googling didn’t turn up v3r error 80 40 that was specific to my issue.

The fix

The answer turned out to be simple, and hinted at in the error message: in the sprers.eu file in the root of your web app, find the roleManager element, and set it to true:

<roleManager enabled="true">

But—and this is what threw me—you must first delete the ASPNETDB_sprers.eu file, and its companion log file with the .ldf extension, from theApp_Data directory, before re-running the Web Site Administration tool. This can be done within Visual Studio. Once this is done, make sure you close the sprers.eu Development server, which will be in the system tray, aka the notification area. Then go back into Visual Studio and launch the Web Site Administration tool. You should now be able to click the Security tab and configure your Roles, etc.

Like this:

This entry was posted on April 6,pm and is filed under sprers.eu, SQL Server, Visual Studio. You error impresora samsung ml-1910 follow any responses to this entry through RSS You can leave a response, or trackback from your own site.

~ Vitalie Ciobanu

Task:

Let&#;s suppose you have Table1 with a million rows and you just altered the table by adding a new column. This new column is empty (NULL) in Table1 but you want to update it with the values that are in a column in Table2.

Solution:

First, do not ruin your day, create a backup table with the same structure and data as TABLE1 by running below query:

Then test the update query by running below query:

If the update went well, run the same query again but replace TABLE1_BKP with TABLE1.

It goes without saying that any UPDATE and Vs error c2248 queries must have a WHERE clause to limit the result as much as possible, in case something unexpected happens. And that&#;s why you need a backup table and test on it first.

~ Vitalie Ciobanu

Started learning how to work with variables in T-SQL. Doing first basic exercise to declare today&#;s date and then print it, failed mizerably.

I was using Toad for SQL because this is my day to day tool. Tried several other examples, searched online for this error&#; looks like &#;it works&#;, but it doesn&#;t for me?!

Opened Microsoft SQL Management Studio, pasted same example, hit F5. Boom, worked! Ok, then it&#;s something related to Toad for SQL.

Searched again with Toad word included, error 5170 microsoft sql server. Of course, found the description quickly on Toad&#;s forum: sprers.eu

This error 5170 microsoft sql server not a bug and that is why things are not changing. This is original behavior from Toad for Oracle.

There are different execution needs depending on what you are doing.

When you have a script you might want to only execute the SQL you are working on. For this you use F9 and we figure out what the current statement is based on your cursor and only execute that.

Or when you have a script you might want to execute all in the script from top down. For this you use F5.

There is a third option which is to execute from the current statement to the end. For this there is a menu action but no hot key.

In the case of a SQL that contains a script variable you can’t execute the current statement as the variable must be declared in block of code that is being sent to the server. So in this case F5 is the only option.

~ Vitalie Ciobanu

Count:

SELECT [ProductModel], COUNT(1) CNT FROM [AdventureWorks].[Production].[vProductAndDescription] GROUP BY [ProductModel] ORDER BY CNT DESC

Count &#;if&#;:

SELECT [ProductModel], [Name],COUNT(1) CNT FROM [AdventureWorks].[Production].[vProductAndDescription] WHERE [ProductModel] LIKE '%Frame' AND [Name] LIKE '%52' --here's the IF statement GROUP BY [ProductModel], [Name] ORDER BY CNT DESC

Count duplicates:

SELECT [ProductModel], COUNT(1) CNT -- select a field you want to search for duplicates in FROM [AdventureWorks].[Production].[vProductAndDescription] GROUP BY [ProductModel] HAVING COUNT(1) > 1 -- if count is greater than 1, then it is a duplicate by that field ORDER BY CNT DESC

Group count fields a tabular form:

SELECT [ProductModel], [Name], COUNT(1) CNT FROM [AdventureWorks].[Production].[vProductAndDescription] GROUP BY [ProductModel], [Name] ORDER BY CNT DESC

~ Vitalie Ciobanu

I had to install a copy of SQL Server on a Windows Server R2 SP2 x During installation I got a strange error saying that SQLncli_xmsi file is missing. I was pretty sure that I have the same ISO file as I did while installing SQL so many times before and without any errors… Searching the net, the solution from Microsoft forum was the right one.

Before installing SQL Server, you have to download and install Microsoft SQL Server Native Client x64 file (sqlncli_xmsi) from Microsoft Download Center.

Note: If you’re going to install Analysis Services too, then make sure to download and install Microsoft SQL Server Management Objects Collectionx64 file (SQLServer_XMO_xmsi) also.

~ Vitalie Ciobanu

Today I again learned a lesson I knew for some time but was hoping that I can forget it. The lesson was about: “Trust anyone. Test for yourself.”

Having to install WSUS on a remote SQL that had WSUS database installed before, I asked one SQL guy if renaming the old WSUS database is enough to install a new WSUS DB. He said &#;yeah, sure!&#;, error 5170 microsoft sql server. Ok then, I started installing WSUS.

Needless to say, installation failed:

Two hours of troubleshooting permission and connection problems, made me read all WSUS installation log files located in “X:\Users\username\AppData\Local\Temp”. One of the file was 1 KB size so it does not contain much error 5170 microsoft sql server. Anyway, the file content was:

One specific line says it all… &#;Cannot create file &#; because it already exists&#;

I guess when doing something, you have to test for yourself everything. Lesson learned. Again.

[KB] ESET Remote Administrator installation error "An error occur during the installation: Code: (0x84bea)"

Issue

  • ESET Remote Administrator all-in-one installation fails during Microsoft SQL Server installation
  • You receive one of the following errors:
    "An error occur during the installation: Code: (0x84bea)"
    "An error occur during the installation: Code: (0x84be)"

Details

The full error message may include the following:

Rule "Setup account privileges" failed.
The account that is running SQL Server Setup does not have one or all of the following rights: the right to back up files and directories, the right to manage auditing and the security log and the right to debug programs. To continue, use an account with both of these rights.

For more information on this SQL htaccess all errors, see the following Microsoft knowledgebase article:

Solution

This error typically occurs when the user does not have sufficient setup account privileges to install the ERA database or the minimum system requirements for the database are not met.

Begin with solution I and only continue to solution II if the issue is not resolved.

I. Verify that your system meets the database requirements for ESET Remote Administrator

You can use an existing Microsoft SQL Server running in your environment; however, it must meet minimum requirements. 

Visit the following Online Help topic: ESET Remote Administrator Database System Requirements

 


II. Ensure that the user has the correct user account privileges

If you intend to use the dedicated database user account that will have access to the ERA database only, you must create a user account with specific privileges before installation. Additionally, you will need to create an empty database that will be used by ESET Remote Administrator.

  1. Ensure the user has the following user rights:
  • SeBackupPrivilege (Back up files and directories)
  • SeDebugPrivilege (Debug programs)
  • SeSecurityPrivilege (Manage auditing and security log)

Check the list of privileges that are currently associated with the account

You can use error 5170 microsoft sql server sprers.eu tool samp has crashed. the error Microsoft: More Information.

  1. To add the user rights to the local administrator account, error 5170 microsoft sql server, follow these steps:
    1. Log on to the computer as a user who has administrative credentials.
       
    2. Click Start  Run, type Control admintools and then click OK.
       
    3. Double-click Local Security Policy.
       
    4. In the Local Security Settings dialog box, click Local Policies, double-click User Rights Assignment and then double-click Backup Files and Directories.
       
    5. In the Backup Files and Directories Properties dialog box, click Add User or Group.
       
    6. In the Select User or Groups dialog box, type the user account that is being used for setup and then click OK two times.
       
    7. Repeat the procedure for the other two policies listed above.
       
    8. Click File and then click Exit to close the Local Security Settings dialog box.
  1. Restart your system and then attempt to install ESET Remote Administrator.

 

For more detailed information on the minimum set of privileges that must be granted to a dedicated database user account, see the following ESET Online Help topic: Dedicated database user account.

 

 

Last Updated: Mar 4,

© - :year ESET, spol. s r.o. - All rights reserved. Trademarks used therein are trademarks or registered trademarks of ESET, spol. s r.o. or ESET North America. All other names and brands are registered trademarks of their respective companies.

SQL Server Filestream: Error when creating database with filestream

I am going through an exercise: How to Detach and Attach a SQL Server FILESTREAM Enabled Database

In the step Creating a FILESTREAM Enabled Database I execute the following code

It all works fine until I run the last step:

When this code is execute I am getting the following error:

MsgLevel 16, StateLine 1 Unable to open the physical file "D:\FileStreamDB\FileStreamData". Operating system error "0x(failed to retrieve text for this error. Reason: )".

I run SQL Server Enterprise (Evaluation Licence) on Windows XP Professional. The filestream is configured as per microsoft instructions

What can be the cause of that error?

asked Mar 3, at

user avatar
padnpadn

1, gold badges silver badges bronze badges

[KB] ESET PROTECT installation error "An error occurred during the installation: Code: (0x84bea)" (8.x – 9.x)

Issue

  • ESET PROTECT all-in-one installation fails during Microsoft SQL Server installation
  • You receive one of the following errors:
    • "An error occurred during the installation: Code: (0x84bea)"
    • "An error occurred during the installation: Code: (0x84be)"

 

Details

The full error message may include the following:

Rule “Setup account privileges” failed.
The account that is running SQL Server Setup does not have one or all of the following rights: the right to back up files and directories, the right to huike 3d anti terrorist auditing and the security log and the right to debug programs. To continue, use an account with both of these rights.

 

For more information on this SQL error, see the following Microsoft Knowledgebase article:

Solution

This error typically occurs when the user does not have sufficient setup account privileges to install the ESET PROTECT database or the minimum system requirements for the database are not met.

Begin with solution I and only continue to solution II if the issue is not resolved.

I. Verify that your system meets the database requirements for ESET PROTECT

You can use an existing Microsoft SQL Server running in error 5170 microsoft sql server environment; however, it must meet minimum requirements. 

Visit the ESET PROTECT database system requirements Online Help topic.

 


II. Ensure that the user has the correct user account privileges

If you intend to use the dedicated database user account that will have access to the ESET PROTECT database only, you must create a user account with specific privileges before installation. Additionally, you will need to create an empty database that will be used by ESET PROTECT.

  1. Ensure the user has the following user rights:
  • SeBackupPrivilege (Back up files and directories)
  • SeDebugPrivilege (Debug programs)
  • SeSecurityPrivilege (Manage auditing and security log)
Check the bittorrent error opening windows firewall windows 7 of privileges that are currently associated with the account

You can use the sprers.eu tool from Microsoft.

  1. To add the user rights to the local administrator account, follow these steps:
    1. Login to the computer as a user who has administrative credentials.
       
    2. Open the Local Security Policy: Press Windows + R, type and then click OK.
    1. In the left pane, expand Local Policies, click User Rights Assignment and then double-click Back up files and directories.
    1. In the Back up files and directories Properties dialog box, click Add User or Group.
    1. In the Select User or Groups dialog box, type the user account that is being used for setup and then click OK two times.
    1. Repeat the procedure for the error 5170 microsoft sql server two policies: Debug programs and Manage auditing and security log.
       
  1. Restart your system and install ESET PROTECT.

 

For more detailed information on the minimum set of privileges that must be granted to a dedicated database user account, see the following ESET Online Help topic: Dedicated database user account.

Last Updated: Aug 5,

© error 5170 microsoft sql server :year ESET, spol. s r.o. - All rights reserved, error 5170 microsoft sql server. Trademarks used therein are trademarks or registered trademarks of ESET, spol. s r.o. or ESET North America. All other names and brands are registered trademarks of their respective companies.

How to fix Microsoft SQL Server Error

Another day of THE DBA chronicles is upon us. This time we are faced with the error that caused a database integrity maintenance plan to fail. Luckily, we set up logging for the plan and a look at the logs showed this detail message:

A database snapshot cannot be created because it failed to start.
Cannot create file &#;E:\Data\BestDatabase_sprers.eu_MSSQL_DBCC92&#; because it already exists. Change the file path or the file name, and retry the operation.

The error message is telling us that it is attempting delphi rename file error create a file in the location ‘E:\Data’ and it has encountered that error 5170 microsoft sql server file already exists.

Further log analysis from the SQL Server Error Log shows below:

spid42      Error:Severity: 16, State: 1.
spid42      Cannot create file &#;E:\Data\BestDatabase_sprers.eu_MSSQL_DBCC92&#; because it already exists. Change the file path or the file name, and retry the operation.

Microsoft’s provisioning of additional details and suggested solutions to the error can, unfortunately, be a bit misleading. Therefore, the focus should not be put on these suggestions as it may not apply to this case. In this scenario, you can&#;t define the physical database snapshot file name when running a Check Database Integrity task.

CAUSE

A dive into the system logs should that the server experienced a system reboot during the run of the DBCC CHECKDB task. What could have caused the server to shut down? Even though this is SQL related and some administrators would not bother to go down this path, it is important you know the root cause and resolve it to prevent any future occurrences. The logs showed that a Windows update was installed which required a server reboot.

Well, that was error 131 pascal to find! How do we resolve that? A few suggestions if you are caught up in this type of issue.

  1. Disable Windows Update
  2. Download Windows Update but Manually Install (Download Only)
  3. Set Work Hours of the server to prevent automatic server reboots from occurring.

Next, we will see how the DBA comes in to resolve the error of

FIX

Find the existing file

  • Using file explorer, navigate to the location of the existing file. In my case, it would be the &#;E:\Data\’. Yes indeed, there was the file that was causing the duplicate conflict during the snapshot creation of the DBCC CHECKDB task.

Fix the error

  1. The fix is as simple as deleting the existing file. However, as all IT professionals know, deletion is a command that is frowned upon. It&#;s better to rename or move the file to have a backup should anything go wrong or need to restore to the previous state.
  2. I also compel that you perform a certain task that I will detail below to make sure that the file is not referenced anywhere else. The least you want is to fix this error and create other issues with other processes or system relying on that file.
  3. The snapshot file can be inspected on the metadata through PowerShell using the CmdLet
    • Get-Item: Get-Item -LiteralPath 'E:\Data\MyDatabase_sprers.eu_MSSQL_DBCC92'
    • As I found no other reference on this error, I deemed it safe to move it to another location as a backup. I could have deleted or renamed the file as well.
  4. How do we know it issue is resolved? We know that a database integrity check kept failing with the error The best way to test is to run an ad-hoc integrity check and it successfully completes, then we can say the error is resolved.
    • DBCC CHECKDB ('BestDatabase');
  5. The test run of the database was successful as shown below:
    CHECKDB found 0 allocation errors and 0 consistency errors in database &#;MyDatabase&#.
    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

error 5170 microsoft sql server alt="" width="" height="">

CONCLUSION

So, there you have it! Another day of THE DBA made simple by providing a solution to anyone that encounters the error Now let’s say you find yourself in a situation where a proper DR plan was not established and the solution provided did not fix the issue, then you rotterdam terror corps silence before the storm consider looking into a third-party database repair tool. Your solution here may be heavily reliant to this third party tool since the SQL out-of-box repair tool (DBCC CHECKDB) is erroring out.

Remember that the repair feature of SQL Server is not robust and not a guaranteed solution. For a error - audit support not in kernel, more versatile repair that would bring your SQL corrupt database back into a working start with minimal data loss, error 5170 microsoft sql server, then look no further with SQL Database Recovery tool. It repairs faster using a more sophisticated repair algorithm. It even can recover deleted data in your database. Click on the link to learn more.

PROBLEM

When GFI Archiver fails to create, attach or upgrade the schema of a Microsoft SQL Server based Archive Store the issue is most likely due to a query against the Microsoft SQL Server failing. Depending on the action being error 5170 microsoft sql server, you might see:

This error in the BulkSchemaUpgrader:


Database schema failed to update


This error in the UI while going through the Archive Store wizard:

There was an error reading from the pipe: The pipe has been cybershot system error c 32 01. (, error 5170 microsoft sql server, 0x6d)


The debug log .\Archiver\Store\DebugLogs\sprers.eu lists runtime error at 69 2161 details:

,,1,"#A0","#","error ","ManagementProviders","Error: (MSSql) CreateDatabase(). Error execute: 
;message: Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQLFIRSTINSTANCE\MSSQL\DATA\ Jan - sprers.eu' because it already exists. Change the file path or the file name, and retry the operation. 
;CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 
;Database ' Jan - Dec' does not exist. Make sure that the name is entered correctly. 
;SqlException. Error No: Error Code: SeverityClass: 16 


Note that above is just an example. The actual error can differ.
  • GFI Archiver
  • Using Microsoft SQL Server as a database backend
  1. Review .\GFI\Archiver\Store\DebugLogs\sprers.eu and find the exact error
    • If the file does not exist cognos dpr-dpr-1035 dispatcher detected an error the lines at the end of the file are not showing a only old time stamps, run .\GFI\Archiver\Enable Debug sprers.eu to enable the error 5170 microsoft sql server mode, then reproduce the issue once again
  2. Address the error found in the previous step (the logged error normally indicates in clear words what the problem is)
  3. Try the action again which previously failed (for example to upgrade the database schema by running .\Archiver\BulkSchemaUpgrader\sprers.eu)
Example #1
"error ","ManagementProviders","Error: (MSSql) UpgradeSchema. Rolling back 
;message: Invalid object name 'sprers.eus'. 

or 

;message: Line Incorrect syntax near '('. 

or

;message: Incorrect syntax near '@userHash'.

This error points towards these 2 scenarios:

a) A Microsoft SQL Server instance is being used which is not supported anymore by current versions of GFI Archiver, error 5170 microsoft sql server. The Bind servfail error SQL Server instance would need to be upgraded to a supported version.

The version of the Microsoft SQL Server instance can be confirmed by running the following query against the instance using the Microsoft SQL Management Studio: SELECT @@VERSION

b) If the databases were hosted on Microsoft SQL Server in the past, but are currently running on a newer and supported version their compatibility level might still be set to 80 (which equals Microsoft SQL Server).

To identify the compatibility level of the databases:
  1. Open the Microsoft SQL Management Studio
  2. Connect to the instance of Microsoft SQL Server which holds the databases of GFI Archiver
  3. Click on View > Object Explorer Details
  4. Open the Databases object
  5. A list of all databases is displayed including a column named compatibility level
The compatibility level of the database must be raised to a higher level (at least to level 90 which equals Microsoft SQL Server ).

To raise the compatibility level of a database:
  1. Open the Microsoft SQL Management Studio
  2. Connect to the instance of Microsoft SQL Server which holds the databases of GFI Archiver
  3. Click on View > Object Explorer Details
  4. Open the Databases object
  5. Right click on a database and click on Properties
  6. Under Select a page choose Options
  7. Raise the Compatibility level to SQL Server (90) or higher
The following article explains how to view or change the compatibility level of a database: sprers.eu

Example #2
UpgradeSchema. Rolling back 
;message: Could not allocate space for object 'sprers.eutobjrefs'.'nc1' in database ' Jan - Dec' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup

In this case the query failed as no further space was available, either on the disk itself, error 5170 microsoft sql server, or because the database size limit was reached (Microsoft SQL Server Express) or because the size of the mdf- or ldf-files is limited within Microsoft SQL Server itself and the limit was reached.

Possible solutions:
  • Increase disk space on the Microsoft SQL Server
  • Remove autogrowth limits within the Microsoft SQL Server database
Example #3
Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQLFIRSTINSTANCE\MSSQL\DATA\ Jan - sprers.eu' because it already exists. Change the file path or the file name, and retry the operation. 
;CREATE DATABASE failed. Runtime error wowmapview file names listed could not be created. Check related errors. 
;Database ' Jan - Dec' does not exist. Make sure that the name is entered correctly. 

In this case the mentioned mdf-file existed in the Microsoft SQL Server data path, but the database was not mounted within Microsoft SQL Server itself.

Possible solutions:
  • Mount the database files in question as a database into the Microsoft SQL Server
  • Move the mdf/ldf files out of the Microsoft SQL Server data folder
Example #4
"error ","ManagementProviders","Error: (MSSql) CreateDatabase(). Error execute: 
;message: MODIFY FILE encountered error 5170 microsoft sql server system error (failed to retrieve text for this error. Reason: ) while attempting to expand the physical file 'E:\Program Files\Microsoft SQL Server\MSSQL10_MSSQLSERVER\MSSQL\DATA\ sprers.eu'. 
;CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 
;SqlException, error 5170 microsoft sql server. Error No: Error Code: SeverityClass: 16

In this case the error indicates insufficient disk space on the drive on which the Microsoft SQL Server database is to be created or Microsoft SQL Server having insufficient access permissions to the folder in which the database is to be created.

Possible solutions:
  • Increase disk space on the Microsoft SQL Server 
  • Ensure that the account under which the Microsoft SQL Server service is running has sufficient NTFS permissions on the path in which the databases are to be created
Example #5
"error ","ManagementProviders","Error: (MSSql) CreateDatabase(). Error execute: 
;message: Could not obtain exclusive lock on database 'model'. Retry the operation later. 
;CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 
;Could not locate entry in sysdatabases for database ' Oct - Dec'. No entry found with that name. Make sure that the name is entered correctly. 
;SqlException. Error No: Error Code: SeverityClass: 16 

This error indicates that another process has a lock on the Microsoft SQL Server's 'model' system database. Whenever Microsoft SQL Server creates a new database it uses the 'model' system databaseas a template requires an exclusive lock on it.

Possible solutions:
  • Restart the Microsoft SQL Server database engine service
  • If running Dell's AppAssure, it seems to be known to cause this situation: sprers.eu
  • Run the following query to identify which process has a lock on the 'model' database, then close this process (the hostname and program_name columns might be the best to look at): SELECT * FROM error lba samsung WHERE DB_NAME(dbid)='model'
Example #6
"info ","ManagementProviders","(MSSql) Upgrading to version [x]. Number of steps to execute [y] >>" 
"info ","ManagementProviders","(MSSql) Step [1] Completed" 
"info ","ManagementProviders","(MSSql) Step [2] Completed" 
"info ","ManagementProviders","(MSSql) Step [3] Completed" 

"error ","ManagementProviders","Error: (MSSql) UpgradeSchema. Rolling back 
;message: Invalid operation. The connection is closed. 

This error indicates a render failed error in sharepoint corruption of the Microsoft SQL Server database.

Possible solutions:
  • Check database integrity using DBCC CHECKDB
  • Restore a healthy backup of the database
Example #7
"error ","ManagementProviders","Error: (MSSql) CreateDatabase(). Error execute: 
;message: CREATE DATABASE permission denied in database 'master'. 
;SqlException. Error No: Error Code: SeverityClass: 14

This error indicates that the SQL login (marc_admin) which GFI Archiver uses to create databases in Microsoft SQL Server does not have sufficient permissions.

Solution:
  1. Open the SQL Management Studio
  2. Connect to the SQL instance
  3. Navigate to: \Security\Logins
  4. Delete any login which begins with: marc_admin (do not delete any other login!)
  5. Open the GFI Archiver web page
  6. Navigate to Configuration > Archive Stores
  7. Click on the New Archive Store Settings button
  8. Go through the wizard
  9. Ensure to use SQL authentication and authenticate with the SA account of the Microsoft SQL Server instance
  10. Complete the wizard
An error occurred while trying to execute a query against the Microsoft SQL Server.

0 Comments

Leave a Comment