Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error exporting single table(s) and also using DTS

Status
Not open for further replies.

cvasquez

MIS
Joined
Feb 28, 2001
Messages
88
Location
US
Setup:
Currently we have two servers. One local and one remote.

Local and remote server are using Windows 2000 server and SQL 2000 server enterprise w/ SP4.

In the past this has always been a problem. But now it is even worse. I tend to believe the problem is in our side and not the remote server. First off, there is a SQL log but for some reason it is not up to date. I have to fix this proble.

Second when I tried to load any table to the remote server the export fails. It fails if I want to create a new table or simple export to existing table having identity check.

The error that I get in SQL is very general. It simply says job failed. No error code. Nothing. Please someone help me. What am I doing wrong?

Carlo
 
I assume you don't have control over the remote machine? Is it in a different domain?

Usually jobs fail between machines on different domains because Pass-through security isn't set up for the domains and/or there's a trust issue.

You say your SQL Log isn't up to date? I'm not sure I understand that, but that's not good. A SQL Log should automatically be logging certain actions.

However, check out your SQL Server Agent Log for job error details. Additionally, when you go to your job screen, right-click the job, and go to view job history. UP at the right hand corner is "Show step details". Check that box and see if you have any additional details on the error message.

Lastly, check your Event Viewer -> Applications and Systems logs to see if there is anything in there.

If you have access to the remote server, do the same on all of those steps and verify that the User Account running the job has the proper permissions for Inserts/Updates, etc. on the remote machine. Make sure you even have DB permissions, etc.





Catadmin - MCDBA, MCSA
"If a person is Microsoft Certified, does that mean that Microsoft pays the bills for the funny white jackets that tie in the back???
 
Well I did what you said here and I ended up rebooting the DBServer. I tried to run a single table again and this time I went with your instructions. This is the error that I get.

Error at Distination for Row number 119. String data, lengh mismatch. [DBNETLIB] [ConnectionWrite(send()).] General Network Error.

Yes the Remote Server is in a different domain.
 
Actually I just found out that the remote server is not even in a domain. It's using a workgroup name. I am not sure what could be causing the problem. The table that I am trying to export is also a little big. More like 8 megs.

Maybe that would help a little bit.

Thanks for the help.


Carlo
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top