xpsmtp80.dll PROBLEMS

Question

Post reply

xpsmtp80.dll PROBLEMS

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply

Brookstone SSCommitted Points: 1745 More actions · Answer 1

Brookstone

SSCommitted

Points: 1745

November 19, 2009 at 11:52 am

#1081760

Not yet. We pointed the process to another server as a work around.

gary1 SSC-Insane Points: 21152 More actions · Answer 2

Hi,

Description

0x8007045A ODSOLE ExtendedProcedure

A dynamic link library (DLL) initialization routine failed.

Source = ODSOLE Extended Procedure, Description = A dynamic link library (DLL) initialization routine failed.

We also have the same issue. We have SQL Server 2005 EE x64 with SP3 on 2 node Clustered Window 2003 EE x64. Rebooting the server solved the problem temporarly. This is a known issue with Windows 2003 Server and theres is a Microsoft Hot fix and we are going to apply this hot fix. Please see the below link

http://support.microsoft.com/kb/941105

Before applying this hot fix, I want to make sure that anybody has applied this patch in a clustered SQL Server 2005?

thanks

Brandie Tarvin SSC Guru Points: 172918 More actions · Answer 3

Unless it's included in SP2 or the SP1 Hot Fix, no. We don't have it applied to our clustered servers.

Of course, the initial solution I posted worked for us, so we didn't actually need to apply the hot fix.

Thanks for point it out, though.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

gary1 SSC-Insane Points: 21152 More actions · Answer 4

Delete or rename the .dll on the server where it's not working. Then add a copy from the server that is working and re-register it. It could be that the copy on the one server is corrupted which means no amount of re-registering will work unless it's replaced.

Your approach may work. But here is the thing:

Even if we follow your approach, if the server is up & running for couple of months and the SQL Services did not start, then it again fails to upload the .dll (I'm assuming) So, I'm thinking to apply the hot fix to fix the issue permanently

We have SQL Server 2005 EE x64 with SP3. Please advcie me know if this issue is addressed in SP3?

Brandie Tarvin SSC Guru Points: 172918 More actions · Answer 5

I'm sure there are a lot of differences between your servers and mine, but this fix was a permanant fix for us. I've had it in affect for almost 2 years now and we haven't had a single problem, regardless of reboots and stalled services.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.