Error 0xC0202009 while preparing to load the package

I have an SSIS project that is deployed to a sql server.

The setup of the project is a parent dtsx package, and many child packages.

The parent executes each of the chid packages.

If I run the parent from BIDS, calling the children that are on the SQL Server, it works fine.

If I execute it from SQL Management Console running on my laptop, connected to the SQL Server, It works.

If I remote into the SQL Server and run it from SQL Agent or SQL Management Console, the job fails with the error:

Error 0xC0202009 while preparing to load the package. SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x%1!8.8X!.

for each of the children.

This has quite suddenly stopped working, and I cannot figure out why it will work being executed from my laptop, but not on the server.

Any ideas?

Thanks

BobP

When you remote in, are you logging in with the same user/password that you use on your laptop? If not, it is probably a problem with security.|||

Yes I am. That's what is stumping me. Since I am running it from SQL Management Studio logged in as the same user, it should run from both machines.

Thanks

BobP

|||The difference is that for the first two scenarios you listed above, you are likely executing them from your machine. That is, dtexec.exe on your machine is executing the packages. When you remote in, you are using the dtexec.exe on the server. This means that things like network connectivity/firewalls/etc... come into play that might not be on your local machine.

What version of SQL Server do you have installed on your local workstation? Do you have the full SSIS client installed?|||

Hey Phil!

I didn't realize that if i run a sql package, logged into SSIS in SQL Management Console that it ran with the DTExec on my machine. Thanks for that bit of info.

However... Yes, I have the full SSIS installed on my machine, and the versions are:

Server 9.0.3042

Workstation: 9.0.3042

The irritating thing about this is that it started happening after it had been working for 2 months.

And as far as I know, nothing has changed on the server.

BobP

|||

BobP - BIM wrote:

However... Yes, I have the full SSIS installed on my machine, and the versions are:

Server 9.0.3042

Workstation: 9.0.3042

More specifically, Standard, Developer, or Enterprise versions? Also, which is installed on the server?|||

Sever is running enterprise 64 bit

Workstation is running developer.

Thanks!

|||

BobP - BIM wrote:

Sever is running enterprise 64 bit

Workstation is running developer.

Thanks!

Okay, so using this arrangement, when connected to Integration Services, through SSMS, you should be executing the copy on the server. That's my understanding.

Has this package run successfully before on a 64-bit machine? Do you have package logging turned on?|||

Nevermind... After a server re-boot, it is working fine now.

Thanks for all the help!

BobP

Error 0x80070003 while loading package file

Hello,
I deployed an SSIS project to my SQL Server. The project I deployed contained two packages. One called the other. After deployment I notice that both packages are indeed in the SQL Server. However when I try to run it I get the error below. This error happens during the "Execute Package Task" and the path the error is pointing at is my local development path, not the one it was deployed to. Is there any way to fix the path? And how can I get it to deploy both packages so it knows where they are when I run it from the server?

Error 0x80070003 while loading package file "C:\VS Projects\Testing\Run Codes to DB\Run Codes to DB\SofAid_DBRefresh.dtsx". The system cannot find the path specified.

Thank You
Jaime
You should use a Package Configuration to populate a variable that specifies where the child package is located. Then use an expression on the connection manager to set the appropriate property from this variable.

You could have a configuration file on your workstation and one on the server, each specifying the appropriate path for that environment. Unless you want to hard-code the location of the file, you might want to specify it's location with an environment variable. Or you could just use an environment variable to hold to package location directly if that's the only configuration information you have.
|||That seems pretty round-about. Is there a way of telling it that the package is in the same folder, or a relative path?
|||No, there's no concept of relative paths in SSIS. Remember that a package may never even exist as a file.
|||You need to use package configuration to set the path and any other property value, dinamically at run time. Serach by package configurations in BOL and this forum.|||Thank you, that was very helpful

error 0x80040155 not interface

Hi

I got the following error message when I make a new integration service project

Failed to save package file "C:\Documents and Settings\Administrator\Local Settings\Temp\1\tmp2B.tmp" with error 0x80040155 "Interface not registered".
Can someone help

MeHi there,

This looks like a setup issue. Did you have a prior build of SQL/VS 2005 on the machine? If so, likely the machine wasn't cleaned up prior to setting up.

regards,
ash|||I also am getting this error.
I upgraded from VS 2005 Beta 2 to VS 2005 RC, but I followed all recommended uninstallation steps prior to installing VS 2005 RC.
So what can I do about this?
Will it help at all to completely uninstall VS 2005 RC and then reinstall it?
I've already tried repairing VS 2005 RC, but it didn't make any difference.
Thanks,
Dyvim|||Try registering MSXML:

regsvr32 msxml3.dll
regsvr32 msxml6.dll|||Thanks, this worked also for me|||Thanks but how do I do this, how do I register MSXML?|||

Just run these two commands from the command prompt:

regsvr32 msxml3.dll
regsvr32 msxml6.dll

|||yes it works for me too. Thanks.|||

I got the same issue, it also works for me.

Thank you so much!

|||

Hi-Thank you for the info. When I ran the 1st command regsvr32 msxml3.dll, it went fine. The 2nd command regsvr32 msxml6.dll told me "The specific module could not be found" I am getting errors like: Interface not registered (when I try to print), No such interface supported (when I tried to contact NoAdware for online support). Also, get same message when I try to go into a game room on Yahoo games. Please note: I just did a scan to remove adware and spyware.

Thanks in advance for any help you can give me,

Corinne

|||

It looks like the software you used to "remove adware and spyware" removed much more - apparently it deleted msxml6.dll (which is installed with SQL Server 2005) and probably some interface registrations.

I would recommend reformatting and reinstalling this machine and avoiding this antispyware program in the future.

|||

Hi, I have the exact same problem but it is when I try to burn a cd using Win Media Player 10. I tried registering the .dll's, but since I don't have the SQL 2005 installed in my machine, the regsvr32 msxml6.dll gives me the same error message. I see that this forum is mainly for SQL but if anybody knows what I can do, it would be appreciated.

Thanks,

Jason

|||

Hi there, di you get a reply to your query as I am experiencing the same problem. Please e-mail me & let me know. Many thanks

|||

Guys, there are thousands of interfaces registered on a typical Windows box. The error can be caused by missing registration of any of them.

We've found that particular problem ("Interface not registered" error when creating new SSIS project) is usually caused by incorrectly registered msxml dlls - my reply above describes how to fix it.

Regarding other applications - like media player, etc - there is no common answer, and you should be looking at the support forums for particular application.

|||

Quote 'I would recommend reformatting and reinstalling this machine and avoiding this antispyware program in the future.'

If I had to re-format every time something is not registering in Windows - that would be all I would be doing -Re-formatting...

Would re-installing SQL fix the problem.

Dan.

Error

Hi. I have a SQL backend and an Access data project front end. Each user has
a local copy of the front end on their computer. I have a function set up to
read data off a CD and import it to the system -- this function works on all
computers except one. On the problematic machine, I keep getting Error 8152
-
String or binary data would be truncated. Here's the line of code that
triggers the error:
DoCmd.RunSQL "UPDATE [Table1] SET [Pub Date] = SUBSTRING([Pub Date], 1, 2) +
'/01/' + SUBSTRING([Pub Date], 3, 4)"
What is happening here is that a number of date fields come into the system
in mm/yyyy format. This causes some problems, so I loaded them into a temp
table as a string, and am inserting 01 for the day in the middle. Once that'
s
complete I'll cast it into a datetime and append the records to the live
data. As I said, this all works for every computer but one. The machine in
question has all the correct Access references, and the user is a member of
the correct group and has all the privileges he needs. Is anyone familiar
with this error? Why would it trigger for one user and not the others?mike wrote:
> Hi. I have a SQL backend and an Access data project front end. Each
> user has a local copy of the front end on their computer. I have a
> function set up to read data off a CD and import it to the system --
> this function works on all computers except one. On the problematic
> machine, I keep getting Error 8152 - String or binary data would be
> truncated. Here's the line of code that triggers the error:
> DoCmd.RunSQL "UPDATE [Table1] SET [Pub Date] = SUBSTRING([Pub Date],
> 1, 2) + '/01/' + SUBSTRING([Pub Date], 3, 4)"
> What is happening here is that a number of date fields come into the
> system in mm/yyyy format. This causes some problems, so I loaded them
> into a temp table as a string, and am inserting 01 for the day in the
> middle. Once that's complete I'll cast it into a datetime and append
> the records to the live data. As I said, this all works for every
> computer but one. The machine in question has all the correct Access
> references, and the user is a member of the correct group and has all
> the privileges he needs. Is anyone familiar with this error? Why
> would it trigger for one user and not the others?
The date format you are using is not a portable format. For a date-only
value, you should use:
YYYYMMDD
David Gugick
Imceda Software
www.imceda.com|||David: Thanks for your response, but the data I'm trying to manipulate is of
type varchar. I handle the date conversion later. Also, the code works just
fine on all the computers except one.
I did some more investigating and discovered that when I try to load data
using the problem computer, the system creates and saves copies of the temp
tables I use for data import and manipulation. All other users re-use the
previously defined tables. The new user-specific temp tables default to data
type nvarchar, rather than varchar. When I switched the appropriate fields
from nvarchar to varchar the code worked fine. Go figure.
"David Gugick" wrote:

> mike wrote:
> The date format you are using is not a portable format. For a date-only
> value, you should use:
> YYYYMMDD
> --
> David Gugick
> Imceda Software
> www.imceda.com
>