![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Invalid OLEVERB structure |
#3
| |||
| |||
|
|
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 |
#4
| |||
| |||
|
|
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 |
#5
| |||
| |||
|
|
"" 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 |
#6
| |||
| |||
|
|
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 |
#7
| |||
| |||
|
|
"" 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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |