Re: Cannot initialize SSPI package

From: Ray Higdon (sqlhigdon_at_nospam.yahoo.com)
Date: 04/22/04 

Date: Wed, 21 Apr 2004 21:24:54 -0400

This may help as well
http://www.sqlservercentral.com/columnists/cmiller/cannotgeneratesspicontext.asp 

-- 
Ray Higdon MCSE, MCDBA, CCNA
---
"Ogie T" <rtorreca@hotmail.com> wrote in message
news:a099ddcd.0404210939.270de9fc@posting.google.com...
> After installing the security updates below, my vb6 applications
> started having problems connecting to the database.
>
> http://www.microsoft.com/technet/security/bulletin/ms04-011.mspx
> http://www.microsoft.com/technet/security/bulletin/ms04-012.mspx
> http://www.microsoft.com/technet/security/bulletin/MS04-014.mspx
>
> I do not have a custom security.dll installed so I know this is not
> the cause of my problem. Searching my entire server will not return
> this file.
>
> System specs:
> Windows 2000 5.00.2195 SP4
> Visual Basic 6.0
> ActiveX ADO 2.5
> IIS 5.0
>
> The applications I have uses a dll for connecting to the database.
> Let's call this dll conn.dll for illustration purposes. Conn.dll
> simply returns an adodb.connection that's already opened. (This way
> when multiple application that need to go to that db, other programmer
> won't need to know the uid/pwd/db. They just need this util to connect
> to it)
>
> I have an .exe that has been running stable for more than 2.5 years
> that uses conn.dll. After applying the patches, it started failing and
> found that it fails with "Cannot Initialize SSPI Package" when
> attempting to connect to db. But the problem does not happen with our
> web applications, which are installed on the same server and also use
> conn.dll to connect to db. Why would it fail on one and not the other?
>
> I also wrote a test .vbs script that uses conn.dll to see if it can
> connect. No problem.
>
> I also wrote another .exe that uses the code snippets from the
> original .exe and it runs without any problems! Again, why would it
> fail on one and not the other when it uses the exact same dll?
>
> So, ok, I remove conn.dll from the .exe and tried to connect using
> straight ADODB.connection with a hard-coded connection string. Still
> fails. But use the same code on a vbscript on the other .exe I
> mentioned, and it works just fine.
>
> I haven't tried uninstalling the patches because it simply is not an
> option at this time as they are critical patches that MUST be
> installed.
>
> If anyone can offer any help, I would greatly appreciate it.
>
> thanks,
> Ogie