Got a bit of a funny here really.
There's 2 problems, but I'm guessing they are related...
The first is:
I have a package that imports a file (in a transform) from the local network, and then does a load of SQL to the imported table to create, ultimately, the required data. Fine. This is the weird bit. The file is imported successfully and when the SQL runs it fails with:
Server: Msg 16882
SQL Web Assistant: Web task not found. Verify the name of the task for possible errors.
The crazy thing is, it doesn't and never has used the Web Assistant. In fact hadn't even heard of it until!
Crazy part number 2: The task runs if I have Internet Explorer running on and connected to the internet on my machine, but still fails if I run the SQL in query analyzer...so what's that all about!?!
This is the bit I am assuming is related (although there is no error message). When the package is called from a job, it only imports the first 6000 (of 36000) rows of data and then bombs out.
I have checked through the data (very boring!!) and I am happy that there is nothing in it that could be making it go mad.
When I have been running the package it has been from my machine. Yet to see what kind of a nightmare will happen if I try running the package from the server
Here's an example of some SQL that calls this error:
CREATE INDEX SAP_CUSTOMER_IDX3
ON SAP_CUSTOMER(CUS_NAME)
ON [PRIMARY]
I'm sure some of you hard core SQL Server people will instantly read this and go - Rob, all you have to do is...
Well, I've tried doing a rain dance and I've tried the usual Microsoft trick of getting things to work (standing up clapping me hands three times, twisting round and finishing with a jump) - but that didn't work either!!
Someone help - I'm going mad
There's 2 problems, but I'm guessing they are related...
The first is:
I have a package that imports a file (in a transform) from the local network, and then does a load of SQL to the imported table to create, ultimately, the required data. Fine. This is the weird bit. The file is imported successfully and when the SQL runs it fails with:
Server: Msg 16882
SQL Web Assistant: Web task not found. Verify the name of the task for possible errors.
The crazy thing is, it doesn't and never has used the Web Assistant. In fact hadn't even heard of it until!
Crazy part number 2: The task runs if I have Internet Explorer running on and connected to the internet on my machine, but still fails if I run the SQL in query analyzer...so what's that all about!?!
This is the bit I am assuming is related (although there is no error message). When the package is called from a job, it only imports the first 6000 (of 36000) rows of data and then bombs out.
I have checked through the data (very boring!!) and I am happy that there is nothing in it that could be making it go mad.
When I have been running the package it has been from my machine. Yet to see what kind of a nightmare will happen if I try running the package from the server
Here's an example of some SQL that calls this error:
CREATE INDEX SAP_CUSTOMER_IDX3
ON SAP_CUSTOMER(CUS_NAME)
ON [PRIMARY]
I'm sure some of you hard core SQL Server people will instantly read this and go - Rob, all you have to do is...
Well, I've tried doing a rain dance and I've tried the usual Microsoft trick of getting things to work (standing up clapping me hands three times, twisting round and finishing with a jump) - but that didn't work either!!
Someone help - I'm going mad