SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


DTS Package fails with error - Invalid OLEVERB structure


DTS Package fails with error - Invalid OLEVERB structure

Author
Message
suresh_yaram
suresh_yaram
SSC Rookie
SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)

Group: General Forum Members
Points: 43 Visits: 20

Dear All,

I have a DTS Package that transfers SQL database objects (Tables & Constraints) from one server to another server using Copy SQL Server Objects Task. I am getting an error as below -

Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:Invalid OLEVERB structure
(Microsoft Data Transformation Services (DTS) Package (80040000): Invalid OLEVERB structure
) (Microsoft SQL-DMO (80004005): [SQL-DMO]CreateFile error on '<servername>.<tablename>.DP2'. )
Step Error code: 80040000
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:1100

Please let me know if anybody has any clue to this error. I have several Copy SQL Server Objects Tasks in the same DTS package. The package has been configured to run 2 tasks in parallel at any point of time. Each time the package fails to tranfer different set of SQL objects.

Thanks in advance,

Suresh





Erik Kutzler
Erik  Kutzler
Right there with Babe
Right there with Babe (781 reputation)Right there with Babe (781 reputation)Right there with Babe (781 reputation)Right there with Babe (781 reputation)Right there with Babe (781 reputation)Right there with Babe (781 reputation)Right there with Babe (781 reputation)Right there with Babe (781 reputation)

Group: General Forum Members
Points: 781 Visits: 1697

Do either of the SQL servers happen to be running under Windows 2003?

Regardless, make sure the "Script File Directory" is valid on the Copy tab of the Copy SQL Server Objects Task properties window.


suresh_yaram
suresh_yaram
SSC Rookie
SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)

Group: General Forum Members
Points: 43 Visits: 20

Yes Erik! Both the servers are residing on Windows 2003 server.

The script file directory is valid. The failure is not happening everyday for the same database. The behaviour is totally inconsistent w.r.t. to the database. Today, the transfer of objects from database A might fail, tomorrow it happens with database B.

Any clue would be appreciated.

Thanks,

Suesh





Dzenan
Dzenan
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 2
I did figure out that you could solve this problem giving modify access (NTFS) to your script file directory for user who crates DTS. At least it helps me
Elaine França Tavares Beraldo
Elaine França Tavares Beraldo
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 1

Hi Suresh,

I have the same problem...

Can you helpme?

Thanks in advance,

Elaine Beraldo


fglazenburg
fglazenburg
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 18
I also fixed the problem by assigning a map with write access to the script path.

Regards,


Frank
francsca bertani
francsca bertani
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 42
we solved it giving access to the user that runs the dts package to the folder:

c:\program files\microsoft sql server\80\tools\
where the file servername.database.LOG is located
norse hedgaardt
norse hedgaardt
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 115
I have this same problem on SQL 2005 SP3 x64...

Error string: Invalid OLEVERB structure



but this is not a permission problem in this case (been done that road already!).

I cannot seem to find any fix for this - anyone else got any suggestions?

I wish and wish Microsoft could produce software that gives error messages that were useful!
Give us the 'where' and 'why', instead of just 'invalid flibflobblbob structure type boll@cks' !!! w00t
gatorspike
gatorspike
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 21
I am researching this same problem on WS2003 and SQL Server 2000. We had ODBC problems after installing security patch "Security Update for Windows Server 2003 (KB2229593)". They were resolved after removing patch. This may be same problem but have not yet done the permission exercise.
Gary Nease
Gary Nease
Valued Member
Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)

Group: General Forum Members
Points: 53 Visits: 457
Mine was caused by name collision between two processes both using instances of the DTS "Copy SQL Server Objects Task" component. It scripts objects to the folder mentioned above, and in my case collided intermittantly on the "<servername>.<dbname>.DP1 or .DP2 files, which it generated identically for two logic branches (one doing schema-only objects, the other doing data-copy). I changed the step-dependency to serialize those steps, and the problem went away. It's a design issue IMHO; the DTS-generated filenames of the parallel processes could have included a guid.


Regards,

Gary
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search