Cannot create BI package get funny error 0x8002801D Library Not

microsoft.public.sqlserver.tools

12 Feb 2006 11:38 PM

Martin

sql server 2005 0x8002801D Library Not registered when opening a temp file?

How do you fix this, tried uninstalling BI and reinstalling same error?

4 Mar 2006 10:10 PM

James

Martin wrote:

> sql server 2005 0x8002801D Library Not registered when opening a temp file?
>
> How do you fix this, tried uninstalling BI and reinstalling same error?

I am getting the same error whe adding an SSIS file to my SQL Server
Integration Services project.

TITLE: Microsoft Visual Studio
------------------------------
Error creating package
------------------------------
ADDITIONAL INFORMATION:

Failed to save package file "C:\Documents and Settings\jacontesse\Local
Settings\Temp\tmp17.tmp" with error 0x8002801D "Library not
registered.".

I guess I have to reregister some DLL but I have no idea which.
The funny thing is that I repaired Visual Studio 2005 and it didn't fix
the problem.
I uninstalled the SQL Server projects and reinstalled them and the
error persists...
Any ideas?

Are all your drivers up to date? click for free checkup

5 Mar 2006 9:26 AM

Martin

Yes, the fix is to run regsvr on these files - then all started working again.

regsvr32 msxml6.dll
regsvr32 msxml3.dll

Some crappy uninstaller must have removed these.

Show quoteHide quote

"James" wrote:

>
> Martin wrote:
> > sql server 2005 0x8002801D Library Not registered when opening a temp file?
> >
> > How do you fix this, tried uninstalling BI and reinstalling same error?
>
> I am getting the same error whe adding an SSIS file to my SQL Server
> Integration Services project.
>
>
> TITLE: Microsoft Visual Studio
> ------------------------------
> Error creating package
> ------------------------------
> ADDITIONAL INFORMATION:
>
> Failed to save package file "C:\Documents and Settings\jacontesse\Local
> Settings\Temp\tmp17.tmp" with error 0x8002801D "Library not
> registered.".
>
>
> I guess I have to reregister some DLL but I have no idea which.
> The funny thing is that I repaired Visual Studio 2005 and it didn't fix
> the problem.
> I uninstalled the SQL Server projects and reinstalled them and the
> error persists...
> Any ideas?
>
>