Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

DTS Package fails with error - Invalid OLEVERB structure Expand / Collapse
Author
Message
Posted Monday, August 28, 2006 6:56 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 2:39 AM
Points: 25, Visits: 8

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




Post #304388
Posted Monday, August 28, 2006 10:44 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Friday, August 31, 2012 10:31 AM
Points: 633, Visits: 1,695

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.

Post #304508
Posted Monday, August 28, 2006 11:25 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 2:39 AM
Points: 25, Visits: 8

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




Post #304522
Posted Tuesday, January 16, 2007 3:19 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, January 07, 2011 7:08 AM
Points: 1, 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
Post #337077
Posted Wednesday, April 04, 2007 1:27 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 04, 2007 1:21 PM
Points: 1, Visits: 1

Hi Suresh,

I have the same problem...

Can you helpme?

Thanks in advance,

Elaine Beraldo

 

Post #356054
Posted Friday, January 04, 2008 12:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, December 22, 2010 2:55 AM
Points: 7, Visits: 18
I also fixed the problem by assigning a map with write access to the script path.

Regards,


Frank
Post #438761
Posted Thursday, February 05, 2009 3:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, January 13, 2014 2:15 AM
Points: 1, Visits: 41
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

Post #650676
Posted Friday, June 05, 2009 5:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 17, 2012 9:43 AM
Points: 5, 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' !!!
Post #729572
Posted Monday, August 02, 2010 10:35 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, January 14, 2014 9:09 AM
Points: 16, Visits: 20
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.
Post #962330
Posted Thursday, November 01, 2012 4:00 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, April 04, 2014 1:54 PM
Points: 23, Visits: 267
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
Post #1380071
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse