I have a custom application that is using xp_cmdshell. I recently moved a copy onto a new server running MS SQL 7 SP4 and Win2000 SP3.
The program uses xp_cmdshell to call stored proc's using Bulk Insert so I can trap errors and log each step in one place.
What happens on the new environment is everything appears to work fine. The Bulk Insert called through xp_cmdshell & isql doesn't throw an error, and returns into @@ROWCOUNT the number of rows loaded. The ERROR is no rows are actually loaded.
The SQL Service is running under a network ID that belongs to the local admin account on the server.
Anyone have any ideas on what else is left to try?
I guess when you move to something new, you overlook the obvious. A new program was added to the batch that truncated the table being loaded. Programmer oversite. The methods work they way they should.