dbTalk Databases Forums  

Invalid OLEVERB structure error 80040000 on DTS job

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Invalid OLEVERB structure error 80040000 on DTS job in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jorge Cavalheiro
 
Posts: n/a

Default Invalid OLEVERB structure error 80040000 on DTS job - 08-17-2005 , 04:49 AM






Greetings.

I have a job that transfers all objects between 2 SQL server 2000 SP3
without problems for several months and tonight it failed this the portion of
error log generated:

DTSRun OnProgress: Copy SQL Server Objects; 100 Percent Completed;
PercentComplete = 100; ProgressCount = 0
DTSRun OnProgress: Copy SQL Server Objects; Scripting completed;
PercentComplete = 0; ProgressCount = 0
DTSRun OnError: Copy SQL Server Objects, Error = -2147221504 (80040000)
Error string: Invalid OLEVERB structure.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 1100


Any suggestion of it means and to solve it?

Thanks

Kind Regards
Jorge Cavalheiro


Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Invalid OLEVERB structure error 80040000 on DTS job - 08-17-2005 , 01:15 PM






Whilst I have not had this error before I would make sure that the source and destination servers were at the same revision of MDAC.

Let us know how you get on

Allan

On Wed, 17 Aug 2005 02:49:04 -0700, "Jorge Cavalheiro" <Jorge Cavalheiro (AT) discussions (DOT) microsoft.com> wrote:

Quote:
Invalid OLEVERB structure

Reply With Quote
  #3  
Old   
Jorge Cavalheiro
 
Posts: n/a

Default Re: Invalid OLEVERB structure error 80040000 on DTS job - 08-18-2005 , 08:12 AM



Resolved by reinstalling sql server on destination pc...

"Allan Mitchell" wrote:

Quote:
Whilst I have not had this error before I would make sure that the source and destination servers were at the same revision of MDAC.

Let us know how you get on

Allan

On Wed, 17 Aug 2005 02:49:04 -0700, "Jorge Cavalheiro" <Jorge Cavalheiro (AT) discussions (DOT) microsoft.com> wrote:

Invalid OLEVERB structure


Reply With Quote
  #4  
Old   
tomshelley
 
Posts: n/a

Default Re: Re: Invalid OLEVERB structure error 80040000 on DTS job - 08-31-2005 , 05:39 PM



"" wrote:
Quote:
Whilst I have not had this error before I would make sure that
the source and destination servers were at the same revision
of MDAC.

Let us know how you get on

Allan

On Wed, 17 Aug 2005 02:49:04 -0700, "Jorge Cavalheiro" <Jorge
Cavalheiro (AT) discussions (DOT) microsoft.com> wrote:

Invalid OLEVERB structure
Hello,

I am having the same issue he discribed with nearly identical error
message. I have verified the MDAC is the same on both machines. MDAC
2.8 sp2.

I just created a copy of the DTS on 3 seperate servers; each nearly
identical to the next. Windows2003 SP1. I updated the DTS to point
to the appropriate server.

Two of them work flawlessly, and one gives this error message.

Any help?

---
tom

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/DTS-Invalid-...ict248813.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=872352


Reply With Quote
  #5  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Invalid OLEVERB structure error 80040000 on DTS job - 08-31-2005 , 06:31 PM



Unfortunately not. As I mentioned I have not had this error. Does Googling get you
anywhere?

Allan


On 31 Aug 2005 18:39:45 -0400, tomshelley <UseLinkToEmail (AT) dbForumz (DOT) com> wrote:

Quote:
"" wrote:
Whilst I have not had this error before I would make sure that
the source and destination servers were at the same revision
of MDAC.

Let us know how you get on

Allan

On Wed, 17 Aug 2005 02:49:04 -0700, "Jorge Cavalheiro" <Jorge
Cavalheiro (AT) discussions (DOT) microsoft.com> wrote:

Invalid OLEVERB structure

Hello,

I am having the same issue he discribed with nearly identical error
message. I have verified the MDAC is the same on both machines. MDAC
2.8 sp2.

I just created a copy of the DTS on 3 seperate servers; each nearly
identical to the next. Windows2003 SP1. I updated the DTS to point
to the appropriate server.

Two of them work flawlessly, and one gives this error message.

Any help?

---
tom

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


Reply With Quote
  #6  
Old   
tomshelley
 
Posts: n/a

Default Re: Re: Invalid OLEVERB structure error 80040000 on DTS job - 08-31-2005 , 09:39 PM



"" wrote:
Quote:
Unfortunately not. As I mentioned I have not had this error.
Does Googling get you
anywhere?

Allan


On 31 Aug 2005 18:39:45 -0400, tomshelley
UseLinkToEmail (AT) dbForumz (DOT) com> wrote:

"" wrote:
Whilst I have not had this error before I would make sure
that
the source and destination servers were at the same
revision
of MDAC.

Let us know how you get on

Allan

On Wed, 17 Aug 2005 02:49:04 -0700, "Jorge Cavalheiro"
Jorge
Cavalheiro (AT) discussions (DOT) microsoft.com> wrote:

Invalid OLEVERB structure

Hello,

I am having the same issue he discribed with nearly identical
error
message. I have verified the MDAC is the same on both
machines. MDAC
2.8 sp2.

I just created a copy of the DTS on 3 seperate servers; each
nearly
identical to the next. Windows2003 SP1. I updated the DTS
to point
to the appropriate server.

Two of them work flawlessly, and one gives this error
message.

Any help?

---
tom


Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you
the new stuff.
www.konesans.com - Consultancy from the people who know
I have discovered the problem!

- The system which was having the problem is a newer 64bit server with
64bit Windows Server 2003.

- The DTS package is using a "Copy SQL Server Objects Task" task.

- I copied this DTS package from a 32 bit Windows Server 2003 system.

The point of all of this is that on the last tab (Copy) in defining
the "Copy SQL Server Objects Task" task contains a textbox
requesting the Script File Directory:. The default value of this
field is the installation location of the SQL Server tools. Typically
found at: C:\Program Files\Microsoft SQL Server\80\Tools

However; on the 64bit system the default location is at: C:\Program
Files (x86)\Microsoft SQL Server\80\Tools

Since I copied this DTS package over to the 64bit system; it was
pointing to an invalid file system location. And this is why I
received the Invalid OLEVERB error.

I would only get that error message in the Job History logs though. I
discovered this was the problem when running the DTS Package without
the job, because it gave me a much more useful error message. It was
something along the lines of, "Invalid specified path defined"
Anyway, it made me look into the package and look specifically for
anything specifying a file path; and that’s exactly what I found.

Thanks for your interest in helping.

---
tom shelley
octfcu

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/DTS-Invalid-...ict248813.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=873350


Reply With Quote
  #7  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Invalid OLEVERB structure error 80040000 on DTS job - 09-01-2005 , 12:30 AM



Wow, good detective work. You are right in that if we had seend the other error message
first then it would have been easy to know what was wrong.

Allan


On 31 Aug 2005 22:39:54 -0400, tomshelley <UseLinkToEmail (AT) dbForumz (DOT) com> wrote:

Quote:
"" wrote:
Unfortunately not. As I mentioned I have not had this error.
Does Googling get you
anywhere?

Allan


On 31 Aug 2005 18:39:45 -0400, tomshelley
UseLinkToEmail (AT) dbForumz (DOT) com> wrote:

"" wrote:
Whilst I have not had this error before I would make sure
that
the source and destination servers were at the same
revision
of MDAC.

Let us know how you get on

Allan

On Wed, 17 Aug 2005 02:49:04 -0700, "Jorge Cavalheiro"
Jorge
Cavalheiro (AT) discussions (DOT) microsoft.com> wrote:

Invalid OLEVERB structure

Hello,

I am having the same issue he discribed with nearly identical
error
message. I have verified the MDAC is the same on both
machines. MDAC
2.8 sp2.

I just created a copy of the DTS on 3 seperate servers; each
nearly
identical to the next. Windows2003 SP1. I updated the DTS
to point
to the appropriate server.

Two of them work flawlessly, and one gives this error
message.

Any help?

---
tom


Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you
the new stuff.
www.konesans.com - Consultancy from the people who know

I have discovered the problem!

- The system which was having the problem is a newer 64bit server with
64bit Windows Server 2003.

- The DTS package is using a "Copy SQL Server Objects Task" task.

- I copied this DTS package from a 32 bit Windows Server 2003 system.

The point of all of this is that on the last tab (Copy) in defining
the "Copy SQL Server Objects Task" task contains a textbox
requesting the Script File Directory:. The default value of this
field is the installation location of the SQL Server tools. Typically
found at: C:\Program Files\Microsoft SQL Server\80\Tools

However; on the 64bit system the default location is at: C:\Program
Files (x86)\Microsoft SQL Server\80\Tools

Since I copied this DTS package over to the 64bit system; it was
pointing to an invalid file system location. And this is why I
received the Invalid OLEVERB error.

I would only get that error message in the Job History logs though. I
discovered this was the problem when running the DTS Package without
the job, because it gave me a much more useful error message. It was
something along the lines of, "Invalid specified path defined"
Anyway, it made me look into the package and look specifically for
anything specifying a file path; and that’s exactly what I found.

Thanks for your interest in helping.

---
tom shelley
octfcu

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.