Cannot install SQL E Service Pack 2 (KB921896)

Hi, i have a clean install of VB2005 Express and it's accompanying SQL Server 2005 Express (yes i'm new to .net).

After installation i ran Windows Update and it found about 40mb of updates including SP1 for SQL Server. All installed correctly up to a reboot point, after which it continued with the update process.

When it reached SP2 (for SQL Server) it tried to install but just says "Updates were unable to be successfully installed" and "The following updates were not installed: Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896)".

Now i have a permanent icon in my system tray which when clicked tries to do the install with the same result.

During the attempted install my floppy drive 'buzzes' a couple of times.

I'm running an AMD3000+ (64bit) cpu with Windows 2000 Pro SP4

As mentioned in another post (on the VB Install forum) my MyDocuments folder is on a networked pc which has caused other non related problems, not sure if this could be responsible for the error. It would seem unlikely as SQL SP1 installed without any errors.

Any help appreciated.

Any official word on this ?|||

Depends on the issue you're encountering, what does the installer log say? You'll find it at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix.

Mike

|||

Hi Mike, not too sure which file you need as the folder you mention contains many files and more folders !

However here is the latest 'summary.txt'

Code Snippet

Time: 04/28/2007 03:01:27.078
KB Number: KB921896
Machine: MyPcName
OS Version: Microsoft Windows 2000 Professional Service Pack 4 (Build 2195)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Express Database Services (SQLEXPRESS) ENU RTM 2005.090.1399.00 x86 EXPRESS
Express Database Services (SQLExpress) ENU RTM x86 EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 70095
Error Description : Unable to install Windows Installer MSI file
-
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 70095
Error Description : Unable to install Windows Installer MSI file
-

**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 70095

However there is also a 'Hotfix.log' file:

Code Snippet

04/28/2007 03:00:24.312 ================================================================================
04/28/2007 03:00:24.312 Hotfix package launched
04/28/2007 03:00:24.343 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
04/28/2007 03:00:24.343 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
04/28/2007 03:00:24.343 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
04/28/2007 03:00:24.343 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
04/28/2007 03:00:24.343 Local Computer:
04/28/2007 03:00:24.343 Target Details: MyPcName
04/28/2007 03:00:24.343 commonfilesdir = C:\Program Files\Common Files
04/28/2007 03:00:24.343 lcidsupportdir = c:\3b642267874f8d43d14991c2\1033
04/28/2007 03:00:24.343 programfilesdir = C:\Program Files
04/28/2007 03:00:24.343 programfilesdir_wow = C:\Program Files
04/28/2007 03:00:24.343 supportdir = c:\3b642267874f8d43d14991c2
04/28/2007 03:00:24.343 supportdirlocal = c:\3b642267874f8d43d14991c2
04/28/2007 03:00:24.343 windir = C:\WINNT
04/28/2007 03:00:24.343 winsysdir = C:\WINNT\system32
04/28/2007 03:00:24.343 winsysdir_wow = C:\WINNT\SysWOW64
04/28/2007 03:00:24.343
04/28/2007 03:00:24.343 Enumerating applicable products for this patch
04/28/2007 03:00:24.343 Found SQL 2005 Express product definition
04/28/2007 03:00:25.250 Enumeration: Determining QFE level for product instance SQLEXPRESS
04/28/2007 03:00:25.265 Enumeration: Associated hotfix build information not found for the following file: c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
04/28/2007 03:00:25.265 Enumeration: Found following QFE level for product instance SQLEXPRESS: 1399
04/28/2007 03:00:25.265 Enumeration: Determining GDR branching Hotfix for product instance SQLEXPRESS
04/28/2007 03:00:25.265 Enumeration: Associated hotfix build information not found for the following file: c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
04/28/2007 03:00:25.265 Enumeration: No GDR branch Hotfix found for product instance SQLEXPRESS
04/28/2007 03:00:25.265 Enumeration: Determining QFE level for product instance
04/28/2007 03:00:25.296 Enumeration: Cannot find following key file for product instance : c:\Program Files\Microsoft SQL Server\90\Tools\\Binn\SQLServr.exe
04/28/2007 03:00:25.296 Enumeration: Determining GDR branching Hotfix for product instance
04/28/2007 03:00:25.296 Enumeration: Cannot find following key file for product instance : c:\Program Files\Microsoft SQL Server\90\Tools\\Binn\SQLServr.exe
04/28/2007 03:00:25.296 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
04/28/2007 03:00:25.296 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
04/28/2007 03:00:25.296 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
04/28/2007 03:00:25.296 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
04/28/2007 03:00:25.296 Product discovery completed during the install process for SQLEXPRESS
04/28/2007 03:00:25.296 SP Level check completed during the install process for SQLEXPRESS
04/28/2007 03:00:25.296 Product language check completed during the install process for SQLEXPRESS
04/28/2007 03:00:25.296 Product version check completed during the install process for SQLEXPRESS
04/28/2007 03:00:25.296 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
04/28/2007 03:00:25.296 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
04/28/2007 03:00:25.296 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
04/28/2007 03:00:25.296 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
04/28/2007 03:00:25.296 Product discovery completed during the install process for SQLExpress
04/28/2007 03:00:25.296 SP Level check completed during the install process for SQLExpress
04/28/2007 03:00:25.296 Product language check completed during the install process for SQLExpress
04/28/2007 03:00:25.296 Product version check completed during the install process for SQLExpress
04/28/2007 03:00:25.296 Command-line instance name check completed during the install process
04/28/2007 03:00:25.296 SKU check completed during the install process for SQLEXPRESS
04/28/2007 03:00:25.296 SKU check completed during the install process for SQLExpress
04/28/2007 03:00:25.296 Baseline build check completed during the installation process for SQLEXPRESS
04/28/2007 03:00:25.296 Baseline build check completed during the installation process for SQLExpress
04/28/2007 03:00:25.296 Baseline build check completed during the install process
04/28/2007 03:00:25.312 Product Enumeration Results:
04/28/2007 03:00:25.312 INF File Name: c:\3b642267874f8d43d14991c2\HotFixExpress.inf
04/28/2007 03:00:25.312 baselinebuild = 1399
04/28/2007 03:00:25.328 build = 3042
04/28/2007 03:00:25.328 description = Express Database Services
04/28/2007 03:00:25.328 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
04/28/2007 03:00:25.328 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
04/28/2007 03:00:25.328 kbarticle = KB921896
04/28/2007 03:00:25.328 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
04/28/2007 03:00:25.328 lcid = 1033
04/28/2007 03:00:25.328 legalproductname = SQL Server Express Database Services 2005
04/28/2007 03:00:25.328 machinetype = x86
04/28/2007 03:00:25.328 package = HotFixExpress
04/28/2007 03:00:25.328 packagetype = SP
04/28/2007 03:00:25.328 productname = SQL9Express
04/28/2007 03:00:25.328 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
04/28/2007 03:00:25.328 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
04/28/2007 03:00:25.328 sku = EXPRESS
04/28/2007 03:00:25.328 splevel = 2
04/28/2007 03:00:25.328 sqlutility = sqlcmd.exe
04/28/2007 03:00:25.328 supportdir = c:\3b642267874f8d43d14991c2
04/28/2007 03:00:25.328 validateauthentication = true
04/28/2007 03:00:25.328 version = 9
04/28/2007 03:00:25.328
04/28/2007 03:00:25.328 File Group Details: EXE
04/28/2007 03:00:25.328 parameters = INSTANCENAME=<NAME>
04/28/2007 03:00:25.328 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
04/28/2007 03:00:25.328 File Details: SQLEXPR.EXE
04/28/2007 03:00:25.328
04/28/2007 03:00:25.328 Instance Details: SQLEXPRESS
04/28/2007 03:00:25.328 clustername =
04/28/2007 03:00:25.328 features = SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
04/28/2007 03:00:25.328 fullversion = 2005.090.1399.00
04/28/2007 03:00:25.328 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.1
04/28/2007 03:00:25.328 id = MSSQL.1
04/28/2007 03:00:25.328 installsqldatadir = c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
04/28/2007 03:00:25.328 installsqldir = c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
04/28/2007 03:00:25.328 lcid = 1033
04/28/2007 03:00:25.328 name = SQLEXPRESS
04/28/2007 03:00:25.328 productcode = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
04/28/2007 03:00:25.328 qfelevel = 1399
04/28/2007 03:00:25.328 servicename = MSSQL$SQLEXPRESS
04/28/2007 03:00:25.328 sku = EXPRESS
04/28/2007 03:00:25.328 sp = 0
04/28/2007 03:00:25.328 type = SQL Server Standalone Product
04/28/2007 03:00:25.328 vermajbld = 1399
04/28/2007 03:00:25.328 version = 9
04/28/2007 03:00:25.328
04/28/2007 03:00:25.328 Instance Details: SQLExpress
04/28/2007 03:00:25.328 clustername =
04/28/2007 03:00:25.328 expressrsstandalone = true
04/28/2007 03:00:25.328 features = Client_Components,Connectivity,SDK
04/28/2007 03:00:25.328 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\Tools
04/28/2007 03:00:25.328 id =
04/28/2007 03:00:25.328 installsqldatadir =
04/28/2007 03:00:25.328 installsqldir = c:\Program Files\Microsoft SQL Server\90\Tools\
04/28/2007 03:00:25.343 lcid = 1033
04/28/2007 03:00:25.343 name =
04/28/2007 03:00:25.343 productcode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
04/28/2007 03:00:25.343 servicename = MSSQL$
04/28/2007 03:00:25.343 sku = EXPRESS
04/28/2007 03:00:25.343 sp = 0
04/28/2007 03:00:25.343 type = Tools Only
04/28/2007 03:00:25.343 vermajbld = 1399
04/28/2007 03:00:25.343 version = 9
04/28/2007 03:00:25.343
04/28/2007 03:00:25.375 Authenticating user using Windows Authentication
04/28/2007 03:00:25.375 SQL Service MSSQL$SQLEXPRESS was previously running, ready for authentication
04/28/2007 03:00:27.640 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
04/28/2007 03:00:27.640 Registry: Cannot read registry key value "PendingFileRenameOperations"
04/28/2007 03:00:27.640 Locked file: Checking for locked files
04/28/2007 03:00:27.640 Attempting to pause the 32 bit ngen queue
04/28/2007 03:00:28.390 Installing product: SQL9Express
04/28/2007 03:00:28.390 Installing instance: SQLEXPRESS
04/28/2007 03:00:28.406 Installing target: MyPcName
04/28/2007 03:00:28.437 Validating database connections using Windows Authentication
04/28/2007 03:00:28.578 Pre-script database connection check was successful - proceeding with script execution
04/28/2007 03:00:29.687 Received list of RANU pid's
04/28/2007 03:00:29.687 Validating database connections using Windows Authentication
04/28/2007 03:00:29.828 Pre-script database connection check was successful - proceeding with script execution
04/28/2007 03:00:29.843 Stopping service: MSSQL$SQLEXPRESS
04/28/2007 03:00:35.875 Stopped service: MSSQL$SQLEXPRESS
04/28/2007 03:00:35.890 Installing file: SQLEXPR.EXE
04/28/2007 03:00:35.890 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
04/28/2007 03:00:35.890 Registry: Cannot open registry key "Software\Policies\Microsoft\Windows\Installer"
04/28/2007 03:01:00.984 EXE returned 70095: *** Shared String ID 200095 Not Found ***
04/28/2007 03:01:00.984 Registry: Cannot open registry key "Software\Policies\Microsoft\Windows\Installer"
04/28/2007 03:01:01.031 Copy Engine: Error, unable to install EXE file: c:\3b642267874f8d43d14991c2\HotFixExpress\Files\SQLEXPR.EXE
04/28/2007 03:01:01.062 The following exception occurred: Unable to install Windows Installer MSI file Date: 04/28/2007 03:01:01.062 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 1653
04/28/2007 03:01:01.703 Watson: Param1 = Unknown
04/28/2007 03:01:01.703 Watson: Param2 = 0x111cf
04/28/2007 03:01:01.718 Watson: Param3 = Unknown
04/28/2007 03:01:01.718 Watson: Param4 = 0x111cf
04/28/2007 03:01:01.734 Watson: Param5 = copyengine.cpp@.1653
04/28/2007 03:01:01.765 Watson: Param6 = Unknown
04/28/2007 03:01:01.765 Watson: Param7 = SQL9Express
04/28/2007 03:01:01.765 Watson: Param8 = @.
04/28/2007 03:01:01.781 Watson: Param9 = x86
04/28/2007 03:01:01.796 Watson: Param10 = 3042
04/28/2007 03:01:01.812 Installed product: SQL9Express
04/28/2007 03:01:01.828 Installing product: SQL9Express
04/28/2007 03:01:01.828 Installing instance: SQLExpress
04/28/2007 03:01:01.843 Installing target: MyPcName
04/28/2007 03:01:01.843 Installing file: SQLEXPR.EXE
04/28/2007 03:01:01.875 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
04/28/2007 03:01:01.875 Registry: Cannot open registry key "Software\Policies\Microsoft\Windows\Installer"
04/28/2007 03:01:26.281 EXE returned 70095: *** Shared String ID 200095 Not Found ***
04/28/2007 03:01:26.312 Registry: Cannot open registry key "Software\Policies\Microsoft\Windows\Installer"
04/28/2007 03:01:26.328 Copy Engine: Error, unable to install EXE file: c:\3b642267874f8d43d14991c2\HotFixExpress\Files\SQLEXPR.EXE
04/28/2007 03:01:26.359 The following exception occurred: Unable to install Windows Installer MSI file Date: 04/28/2007 03:01:26.359 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 1653
04/28/2007 03:01:26.968 Watson: Param1 = Unknown
04/28/2007 03:01:26.968 Watson: Param2 = 0x111cf
04/28/2007 03:01:26.968 Watson: Param3 = Unknown
04/28/2007 03:01:26.968 Watson: Param4 = 0x111cf
04/28/2007 03:01:26.984 Watson: Param5 = copyengine.cpp@.1653
04/28/2007 03:01:26.984 Watson: Param6 = Unknown
04/28/2007 03:01:26.984 Watson: Param7 = SQL9Express
04/28/2007 03:01:26.984 Watson: Param8 = @.
04/28/2007 03:01:26.984 Watson: Param9 = x86
04/28/2007 03:01:26.984 Watson: Param10 = 3042
04/28/2007 03:01:26.984 Installed product: SQL9Express
04/28/2007 03:01:26.984 Hotfix package completed
04/28/2007 03:01:27.000 Attempting to continue the 32 bit ngen queue

Hope this is the info you needed ?

|||

I had this problem

i backed up all my databases, uninstalled the whole sha-bang and started over. worked like a charm second time around. (this time my sql express is on the default instance also, the only thing different i can think of)

Cannot install SQL 2000 Reporting Services on W2K3 server

Hi ALL,
I want to install SQL 2000 Reporting Services Component on a Windows Server
2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
message 'System Check Results --> ASP.NET is not installed or is not
registered with your Web Server". However, I'd checked the Web service
extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
the Reporting Services Database on the SQL 2000 cluster?
TIA.Hi, I have the same problem, I "only" have the error that I dont have asp.net
installed or configured, despite that it is installed and configured, I have
both asp.net 1.1 and 2.0, I have tried to switch between both, but the result
is the same error, any ideas? Have you got a solution yet?
DQ
"M C" wrote:
> Hi ALL,
> I want to install SQL 2000 Reporting Services Component on a Windows Server
> 2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
> message 'System Check Results --> ASP.NET is not installed or is not
> registered with your Web Server". However, I'd checked the Web service
> extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
> v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
> the Reporting Services Database on the SQL 2000 cluster?
> TIA.
>
>|||SOLUTION that helped me!!
FIX: Error "ASP.NET v1.1 not Installed" while installing Sql Server 2000
Reporting Services
I finally had the chance to rebuild my dev machine with the RTM version of
Sql Server 200 Reporting Services [SQL2kRS] and ran into an unusual error.
During the "Check Prerequisites" stage of installation, it said that I didnt
have ASP.NET v1.1 installed on my PC. Considering that I do web-development
with VS.NET 2003 on this PC I was a bit perplexed why it said that.
After much digging and exploring, I finally discovered the problem. A
recent install of the new XP version of the Longhorn Command Shell had
installed the .NET Framework v2.0.31113.33 and set it as the Root Version of
the framework for ASP.NET.
So, the fix is pretty trivial, just update the RootVer registry value to
correctly (or temporarily) show v1.1.4322.573.
[\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"
Strangely enough, this didnt seem to be affecting my ASP.NET applications.
*shrug*
None of this was documented in the verbose Help files that shipped with
SQL2kRS. This got me thinking about the nature of help files. Far too
often, I see FAQ's and "Common Issues" under the Troubleshooting section of
help files, yet rarely do I have those "common" problems.
I would much prefer a generic section on, "How to troubleshoot", "Where to
look for error clues", and provide deep lists of "Why an application or
installation might fail".
In this case, I actually did find a good reference in the Help entitled "Log
Files Used During Installation". This section explained how to locate the
log files created during installation, and this is how I eventually solved
the problem.
For reference, in SQL2kRS there are 3 main places to look for log files;
C:\Program Files\Microsoft SQL Server\80\RS Setup Bootstrap\Log\RSStp_.cab
(inside the CAB)
AND
%temp%\rsstp<integer>.log
(<integer> = number to make filename unique. e.g. rsstp2.log)
AND
%temp%\RSMSI<integer>.log
The latter 2 log files are the same ones that get copied into the CAB file
listed above, but its still useful knowledge in case something fails before
they get added to the CAB.
"DQ" wrote:
> Hi, I have the same problem, I "only" have the error that I dont have asp.net
> installed or configured, despite that it is installed and configured, I have
> both asp.net 1.1 and 2.0, I have tried to switch between both, but the result
> is the same error, any ideas? Have you got a solution yet?
> DQ
>
> "M C" wrote:
> > Hi ALL,
> >
> > I want to install SQL 2000 Reporting Services Component on a Windows Server
> > 2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
> > message 'System Check Results --> ASP.NET is not installed or is not
> > registered with your Web Server". However, I'd checked the Web service
> > extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
> > v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
> > the Reporting Services Database on the SQL 2000 cluster?
> >
> > TIA.
> >
> >
> >

cannot generate sspi context when server in mixed authentication m

We have a situation for which I have been trying to find an explanation for
over a week. A windows 2005 SP1 server which previously ran in Windows
authentication only suddenly caused "cannot generate sspi context" errors
after we switched it to mixed authentication mode.
-SQL service is running with domain account not trusted for delegation
-We have checked for invalid SPNs in the domain and there are none
registered for the SQL Service on this machine
-TCP/IP protocol is enabled on the server
-Named Pipes connections work fine
-After switching back to Windows authentication and clearing the ticket
cache the problem dissapears
If I understand correctly. The default authentication protocol used over
tcp/ip when connecting to SQL Server is Kerberos but if the client cannot
find a valid SPN for the SQL Service on the server then it should fall back
to NTLM. For some reason however, this is not happening as it should.
What is SQL Server service starting as...local system, domain user or domain
admin?
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:65AFAA64-4847-4034-8745-211ED18ACB0E@.microsoft.com...
> We have a situation for which I have been trying to find an explanation
> for
> over a week. A windows 2005 SP1 server which previously ran in Windows
> authentication only suddenly caused "cannot generate sspi context" errors
> after we switched it to mixed authentication mode.
> -SQL service is running with domain account not trusted for delegation
> -We have checked for invalid SPNs in the domain and there are none
> registered for the SQL Service on this machine
> -TCP/IP protocol is enabled on the server
> -Named Pipes connections work fine
> -After switching back to Windows authentication and clearing the ticket
> cache the problem dissapears
> If I understand correctly. The default authentication protocol used over
> tcp/ip when connecting to SQL Server is Kerberos but if the client cannot
> find a valid SPN for the SQL Service on the server then it should fall
> back
> to NTLM. For some reason however, this is not happening as it should.
>
|||It is starting with a domain user account.
"Kevin3NF" wrote:

> What is SQL Server service starting as...local system, domain user or domain
> admin?
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "DBA72" <DBA72@.discussions.microsoft.com> wrote in message
> news:65AFAA64-4847-4034-8745-211ED18ACB0E@.microsoft.com...
>
>
|||A domain admin will need to create an SPN for the SQL Server service
manually using SetSPN or ADSI (I think)
Local system or domain admin starting sql does this automatically...domain
user does not
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:F01518D8-9430-49AB-95AC-076BF1C5CF84@.microsoft.com...[vbcol=seagreen]
> It is starting with a domain user account.
> "Kevin3NF" wrote:
|||"Kevin3NF" wrote:

> A domain admin will need to create an SPN for the SQL Server service
> manually using SetSPN or ADSI (I think)
> Local system or domain admin starting sql does this automatically...domain
> user does not
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "DBA72" <DBA72@.discussions.microsoft.com> wrote in message
> news:F01518D8-9430-49AB-95AC-076BF1C5CF84@.microsoft.com...
>
Kevin,
I think you would be right if I was trying to use Kerberos but as I said,
this is not enabled for the sql service account. What I want to do is use
NTLM over tcp/ip
|||If you are getting SSPI error, something is attempting to use
Kerberos...even if that was not your intention. This is more of an Active
Directory issue than SQL Server, so I'm pretty much at the end of my
knowledge base...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:6C11E262-B916-42BA-A294-A16FD71FE5C0@.microsoft.com...
>
> "Kevin3NF" wrote:
> Kevin,
> I think you would be right if I was trying to use Kerberos but as I said,
> this is not enabled for the sql service account. What I want to do is use
> NTLM over tcp/ip

cannot generate sspi context when server in mixed authentication m

We have a situation for which I have been trying to find an explanation for
over a week. A windows 2005 SP1 server which previously ran in Windows
authentication only suddenly caused "cannot generate sspi context" errors
after we switched it to mixed authentication mode.
-SQL service is running with domain account not trusted for delegation
-We have checked for invalid SPNs in the domain and there are none
registered for the SQL Service on this machine
-TCP/IP protocol is enabled on the server
-Named Pipes connections work fine
-After switching back to Windows authentication and clearing the ticket
cache the problem dissapears
If I understand correctly. The default authentication protocol used over
tcp/ip when connecting to SQL Server is Kerberos but if the client cannot
find a valid SPN for the SQL Service on the server then it should fall back
to NTLM. For some reason however, this is not happening as it should.What is SQL Server service starting as...local system, domain user or domain
admin?
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:65AFAA64-4847-4034-8745-211ED18ACB0E@.microsoft.com...
> We have a situation for which I have been trying to find an explanation
> for
> over a week. A windows 2005 SP1 server which previously ran in Windows
> authentication only suddenly caused "cannot generate sspi context" errors
> after we switched it to mixed authentication mode.
> -SQL service is running with domain account not trusted for delegation
> -We have checked for invalid SPNs in the domain and there are none
> registered for the SQL Service on this machine
> -TCP/IP protocol is enabled on the server
> -Named Pipes connections work fine
> -After switching back to Windows authentication and clearing the ticket
> cache the problem dissapears
> If I understand correctly. The default authentication protocol used over
> tcp/ip when connecting to SQL Server is Kerberos but if the client cannot
> find a valid SPN for the SQL Service on the server then it should fall
> back
> to NTLM. For some reason however, this is not happening as it should.
>