Problem with ADO Dataset Iterator

Automise Discussion
1


This is a script that simply selects records (there are only two) from a table on a SQL 2000 server and then checks for a few things.

It was working fine up until a month ago. The only changes made are some Windows update on the Windows 2003 box.

It fails on the first step, running an ADO Dataset Iterator with the following error:

    [ADO Dataset Iterator [ select * from tblSomeTable]]
      Error : The connection cannot be used to perform this operation. It is either closed or invalid in this context
      The iterator could not be initialised.
 

The thing is, it works fine on my Windows 7 development machine, but as soon as I put it on the Windows 2003 box it starts giving that error.


Any ideas?

Thanks in advance!

2

 Is the username/password specified (explicit) in the connection string? If no, then it could be that your vista machine username has access to the DB but the server 2003 machine does not have access.

3

Thanks for the reply.

 

Yes, the SQL server user name and password is stored in the connection string (I can see it Automise in plain text). In this case, MSSQL is configured for mixed auth. The account is db_owner on the database in question.

I've also tried both the SQL Native Client (which was workign) and the ODBC one. Both work on my Windows 7 PC, but not on the Windows 2003 server.

I've already (as best I can tell) ruled out paths, and other problems (working my way up the OSI layers, this seems to be app layer). This is literally the first line in the Automise script.

To simplify,I even tried creating just a test project with one step that connects to the Northwind database on that server and selects anything with the same result. The odd thing is that I have the same version of the Automise runtime on both machines.

 

4

Hi Isaac

Your simple test that queries the Northwind database, did you use the ADO Dataset Iterator action or the ADO Execute SQL action to perform this test?

Are you able to determine whether the script has run successfully after the Windows updates were applied? I suspect a Windows update may have changed your ADO configuration. If you have some way of determining when the script last ran successfully on this machine and then check which updates were installed relative to this date, you may be able to narrow down which updates caused this issue.

Regards,
Steve