August 2, 2007 at 12:18 pm
I'm trying to modify one of my maintenance plans that's just a simple backup. When I click the save button I get the following message: Library not registered.
It has no information on what library is not registered. This is happening on the actual SQL Server.
If I try doing this on a remote server I can't even open up the designer because I get the following pop-up message: Value cannot be null. Parameter name: component (System.Design)
In SSMS it says: Microsoft SQL Server Management Studio is unable to load this document: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Cannot generate SSPI context). The SQL Statement that was issued has failed.
I think I get this error because I am connected to the server using Named Pipes since TCP/IP connection gives me that famous "cannot generate sspi context" error but when SSMS tries to open up the maintenance plan it still trying to use TCP/IP.
So right now I'm stuck, I cannot create new maintenance plans nor modify existing ones. Any suggestions?
August 2, 2007 at 2:20 pm
I found solution for the "Library not registered" error on another board. I had to register the following two dlls: msxml6.dll and msxml3.dll.
But if anyone has suggestions for the "cannot generate sspi context" issue, I'd really appreaciate it.
August 2, 2007 at 11:15 pm
Generall SSPI messages are related to windows authentication/integrated security... are you running as a domain user (or a non-domain user)? Is the server a member of a domain?
Joe
August 3, 2007 at 8:57 am
The SQL Server service is running under a domain account that is not a domain admin. At one point I made it part of domain admins just to see if that would fix the problem but no, the error message persisted. The reason why we are not using the local service account to run the service is because of off-server backups. The server is part of the domain.
August 6, 2007 at 3:57 pm
Registering these 2 DLLs should fix your problem.
regsvr32 msxml6.dll
regsvr32 msxml3.dll
Randy
April 8, 2008 at 8:19 am
Hi,
A server is not a domain member could be the reason why it generate that error.
Thnx
October 7, 2008 at 6:07 am
Registering the DLLs fixed the problem
October 26, 2008 at 11:03 pm
Yes, registrering those two msxml dlls fixed the problem.
April 8, 2009 at 10:52 am
does anyone know the reason that this brakes?
May 15, 2009 at 1:54 am
randy wen (8/6/2007)
Registering these 2 DLLs should fix your problem.
regsvr32 msxml6.dll
regsvr32 msxml3.dll
Randy
How to register?
May 19, 2009 at 3:14 pm
Go to start - run
type "cmd" and hit enter
in the MS DOS window, type those two commands (one at a time)
October 5, 2009 at 2:48 am
can any one advise me y this error "library not registered " is coming...some times before i was able to make changes in maintanence plan
January 18, 2010 at 12:39 pm
Randy,
I followed your instruction. It solved my problem.
Thank you so much.
March 24, 2010 at 8:59 am
Hi Randy,
I just have red the solution you gave for the problem with "Library not registered" because I have the same issue and I don't know how register it...¿I just need to enter the the instructión regsvr32 msxml6.dll from CMD?
Thanks
++++++++++++++++
Registering these 2 DLLs should fix your problem.
regsvr32 msxml6.dll
regsvr32 msxml3.dll
Randy
++++
September 9, 2010 at 6:00 am
[font="Tahoma"]Yes, registering the two dlls worked with as just fine.
As for the execution we changed path on "cmd" to where the dlls where:
cd c:\WINDOWS\System32.
,and then we executed the two regsvrcommands.
Now the maintenance plans are saved just fine.
Thanks a lot[/font]
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply