Archive for the ‘SQL Error Messages’ Category

SQL Server 2005 SP3 and above is supported on Windows 7. Trying to install this I ran into the catch 22 situation: it won’t let me install SQL Server as only SP 3 and over is supported. I can’t install the service pack until SQL is installed. You can have hours of fun like this.

You may be able to get a SQL Server 2005 disc with SP3 applied but I couldn’t find one. What I did find was that it let me install developer edition. After that I installed SP4. Then I upgraded to Enterprise.

That all sounds too easy…

Of course it didn’t let me install developer edition just like that. It had to fail a couple of times first. The failure reported that SQLNCLI.msi was missing. It was there so I tried again. It failed. I then did some searching and found that this was because an earlier version of the client was installed. I went to add remove programs and removed it. After that the install went through OK.

This link will take you to my previous post on upgrading SQL Server 2005

Advertisements

If you look in the SQL Agent error logs it should record the problem – Subsystem %s could not be loaded.

When this happens you need to run this script:

use msdb;
delete from msdb.dbo.syssubsystems;
exec msdb.dbo.sp_verify_subsystems 1;
go

Now restart the SQL Agent

Reference

http://support.microsoft.com/?kbid=914171

Error Message in SSMS

TITLE: Microsoft SQL Server Management Studio

——————————

Cannot show requested dialog.
——————————

ADDITIONAL INFORMATION:

Cannot show requested dialog. (SqlMgmt)

——————————
There is no row at position 0. (System.Data)

Problem is to do with system table spt_values being deleted.

Run this script to repair – the location may be different on your server.
C:\Program Files\Microsoft SQL Server\MSSQL\MSSQL.1\install\u_tables.sql

TITLE: Microsoft SQL Server Management Studio
——————————

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

——————————
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

——————————

The EXECUTE permission was denied on the object ‘xp_prop_oledb_provider’, database ‘mssqlsystemresource’, schema ‘sys’. (Microsoft SQL Server, Error: 229)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4266&EvtSrc=MSSQLServer&EvtID=229&LinkId=20476

FIX
GRANT EXECUTE ON xp_prop_oledb_provider TO [UserDomain\Account Name];

BIDS Helper is deploying packages…
Deploying to SQL Server MSDB on server: NAMEOFSERVER
Error : BIDS Helper encountered an error when deploying package PACKAGENAME.dtsx!
“c:\Program Files\Microsoft SQL Server\90\DTS\binn\dtutil.exe” /FILE “PATHTOPACKAGE.dtsx” /DestServer NAMEOFSERVER /COPY SQL;”Package” /Q
exit code = 6
Microsoft (R) SQL Server SSIS Package Utilities
Version 9.00.4035.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2004. All rights reserved.
Could not save package “PACKAGE” because of error 0x80004005.
Description: Cannot open database “msdb” requested by the login. The login failed.
Source: Microsoft SQL Native Client

Had to give the user’s account access to msdb and the dts_admin and dts_operator roles.

I ran a query which resulted in this:
An error occurred while executing batch. Error message is: The directory name is invalid.

The reason for this was an invalid temp directory. The system was pointing at c:\temp but the directory did not exist. I re-pointed all the temp and tmp environment variables at the real temp directory and all was well again.