Showing posts with label throws. Show all posts
Showing posts with label throws. Show all posts

Friday, February 24, 2012

change sqlvdi.dll IdentifySQLServer

I've inherited a SQL 2005 Server with SP2 installed that throws this error whenever it's backed up via EMC Insignia's Retrospect 7.5:

Source: SQLVDI
Event ID: 1

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY1. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=4788. Thread=4672. Client. Instance=DATALIBRARY1. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As far as I can tell, the name should be DATALIBRARY, not DATALIBRARY1. Is there a way to change that reference without having to uninstall / reinstall?

Thanks,

- Al

If the SQL instance is named DATALIBRARY, then you'll need to look at the Retrospect configuration to see why it's using the wrong name. It may be as simple as revising the Retrospect backup job. I don't have a copy of Retrospect to play with, so I can't tell exactly how that would be done.|||Thanks Kevin. After uninstalling / re-installing the Retrospect client countless times, I was finally able to get it to sync with the SQL instance DATALIBRARY. Now I'm getting the same error message with the correct server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other ideas / troubleshooting I can try?

Thanks,

- Al

|||Thanks Kevin.

I uninstalled / re-installed the Retrospect client and was able to get the client to sync up with the correct SQL instance name. Now the error message is the same, except that it points to the correct name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting you can think of?

Thanks,

- Al

|||Thanks Kevin,

I uninstalled / re-installed the Retrospect client and was able to pick up the correct SQL instance name. Now we're logging the same error with the right server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting tips I can try?

Thanks,

- Al

change sqlvdi.dll IdentifySQLServer

I've inherited a SQL 2005 Server with SP2 installed that throws this error whenever it's backed up via EMC Insignia's Retrospect 7.5:

Source: SQLVDI
Event ID: 1

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY1. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=4788. Thread=4672. Client. Instance=DATALIBRARY1. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As far as I can tell, the name should be DATALIBRARY, not DATALIBRARY1. Is there a way to change that reference without having to uninstall / reinstall?

Thanks,

- AlIf the SQL instance is named DATALIBRARY, then you'll need to look at the Retrospect configuration to see why it's using the wrong name. It may be as simple as revising the Retrospect backup job. I don't have a copy of Retrospect to play with, so I can't tell exactly how that would be done.|||Thanks Kevin. After uninstalling / re-installing the Retrospect client countless times, I was finally able to get it to sync with the SQL instance DATALIBRARY. Now I'm getting the same error message with the correct server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other ideas / troubleshooting I can try?

Thanks,

- Al|||Thanks Kevin.

I uninstalled / re-installed the Retrospect client and was able to get the client to sync up with the correct SQL instance name. Now the error message is the same, except that it points to the correct name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting you can think of?

Thanks,

- Al|||Thanks Kevin,

I uninstalled / re-installed the Retrospect client and was able to pick up the correct SQL instance name. Now we're logging the same error with the right server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting tips I can try?

Thanks,

- Al

change sqlvdi.dll IdentifySQLServer

I've inherited a SQL 2005 Server with SP2 installed that throws this error whenever it's backed up via EMC Insignia's Retrospect 7.5:

Source: SQLVDI
Event ID: 1

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY1. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=4788. Thread=4672. Client. Instance=DATALIBRARY1. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As far as I can tell, the name should be DATALIBRARY, not DATALIBRARY1. Is there a way to change that reference without having to uninstall / reinstall?

Thanks,

- AlIf the SQL instance is named DATALIBRARY, then you'll need to look at the Retrospect configuration to see why it's using the wrong name. It may be as simple as revising the Retrospect backup job. I don't have a copy of Retrospect to play with, so I can't tell exactly how that would be done.|||Thanks Kevin. After uninstalling / re-installing the Retrospect client countless times, I was finally able to get it to sync with the SQL instance DATALIBRARY. Now I'm getting the same error message with the correct server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other ideas / troubleshooting I can try?

Thanks,

- Al|||Thanks Kevin.

I uninstalled / re-installed the Retrospect client and was able to get the client to sync up with the correct SQL instance name. Now the error message is the same, except that it points to the correct name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting you can think of?

Thanks,

- Al|||Thanks Kevin,

I uninstalled / re-installed the Retrospect client and was able to pick up the correct SQL instance name. Now we're logging the same error with the right server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting tips I can try?

Thanks,

- Al

Sunday, February 12, 2012

Change ntext to nvarchar(max) in a live database

I have a live SQL 2005 database that has ntext fields, when the ntext fields go over 4000 chars the record can no longer be edited. It throws a string or binary data would be truncated error. I tried turning text in row OFF, but it did not work. Can anyone forsee any problems with changing the ntext fields to nvarchar(max) in the live database? Also, I came across sp_tableoption N'MyTable', 'large value types out of row', 'ON', does this work for ntext also? sp_tableoption N'MyTable', 'text in row', 'OFF' did not do anything.

Any help would be appreciated.

Have you set TEXTSIZE option for the connection? Check this using:

DBCC USEROPTIONS

|||

Where and how do I do this? Also I changed the ntext fields in the database to NVarChar(MAX), so now I can modify the values in the database directly, but when I do it through the application and the VarChar(MAX) fields are over 4000 it does not save the changes, but does not return an error either. It returns as if the stored procedure executed successfully.

|||

I'm not sure why you felt the need to create yet another thread, but the answer remains the same (and the 3rd time I'm giving it to you):

The problem is more likely that the parameters are being declared as either the wrong type, or you are not declaring the type at all, and letting it default. Make sure your ntext parameters are declared as such.

|||

Actually it was a problem upgrading a SQL 2000 database to SQL 2005 then modifying it, I had to recreate the table. Once I recreated the table and did a Select Into, the problem was resolved.

And I created another thread because I wanted to change the datatypes from ntext to nvarchar(max) in a live database and wanted to know if it was going to have any ill effects. In my experience, when you ask a different question in an existing thread, you do not get an answer for both questions, so I wanted to keep them separated.