Exception Access Violation 1

[KevinFSI]

This problem is machine specific since I was able to do the exact same thing on our live machine yesterday, but not our dev machine. Here 'tis:

When trying to EXPORT a table from the dev machine to the live machine using DTS wizard, I select:

* MSFT OLE DB for SQL Server
* my source DB

then

* MSFT OLE DB for SQL Server
* my destination DB

then

* Transfer objects between SQL Server DBs
* Select the table I want to transfer
* Select the other options I want (none of which could be
  causing this problem)
* Click finish

Then it starts the data transformation but gives me the following error:

******************************************************
   Need to run the object to perform this operation

   [SQL-DMO]Code Execution Exception:
             EXCEPTION_ACCESS_VIOLATION
******************************************************

Any thoughts? I can tell you that I did the exact same thing on the live machine using IMPORT instead of EXPORT with all the same settings and it worked fine.

Also, on the dev machine, if I choose "copy tables..." rather than "transfer objects..." it works fine. But I know I've done it many times before using "transfer objects..." Someone please offer some insight before I pull the last strand of hair out of my head!

Using:
NT4 SP5
SQL7 SP2 (MDAC 2.5)

Kevin
slanek@ssd.fsi.com

 

[tlbroadbent]

The following Microsoft Knowledgebase article may solve your problem.

http://support.microsoft.com/support/kb/articles/Q268/4/13.ASP

 

[KevinFSI]

Wow, that was it!!! The only difference is that the article mentions the local server, where in my case it is the destination server that needs renaming.

I must have been all over that knowledge base over the past two days! What in the world did you type in to get that article?

Thanks a million! Kevin
slanek@ssd.fsi.com

 

[tlbroadbent]

I searched the knowledgebase for the phrase "Need to run the object to perform this operation".

 

[KevinFSI]

Crap! I was searching for every possible combo of "exception access violation." Thanks again. Kevin
slanek@ssd.fsi.com

 

[KevinFSI]

Hey, what do you know about performing the steps in that article? Let me give you the rundown.

If I type select @@servername on my dev server, I get the proper name. If I type it on my live server it returns NULL. If I try to do what the article said which is:

sp_addserver 'servername', local

for a machine that returns NULL it tells me that the name is already in use. There is no other server with that name. It says I can run this code:

sp_dropserver 'servername'
go
sp_addserver 'servername', local

But that's IF select @@servername returned the wrong server name.

Since it's telling me that my servername is already being used, I thought that might be an option, but do you know what effect that might have on a live server? Kevin
slanek@ssd.fsi.com