SIMS and USO AutoUpdate

[CallMeMonks]

Just wondering if someone could help me out with a strange issue we are having with USO AutoUpdate from LGfL. LGfL are saying it's a SIMS fault... SIMS support are saying it's an USO AutoUpdate fault!

 

So, we've just migrated to a new SIMS server, we've installed USO AutoUpdate on the new server, put in all the details, including licensing information and a SIMS user account (a different SIMS user account from the previous server but the user has the required permissions). Everything checks out OK and the software loads just fine. Carry out a report run from within the USO AutoUpdate software and everything works just fine. Set up a scheduled task and it doens't work via that method. We keep getting the following error in the log file:

 

03/09/2020 14:00:46:0:Config loaded OK

03/09/2020 14:00:48:10:CommandReportImporter:

SIMS.net Command Line Report Importing Utility 7.194.22.0

Copyright ¸ Capita Business Services Ltd 1984-2020. All rights reserved.

Login failed for user AutoUpdate

Incorrect S:\SIMS\Connect.ini file

 

The S drive is mapped to the SIMS data folder. The Connect.ini file is the correct file. SIMS works just fine on the server running the USO AutoUpdate software and we are able to log in with the AutoUpdate user. Does anyone have any ideas what's going on?

[5tu]

It's been years since we had USO AutoUpdate but I do remember having the same issue which was down to s:\ not existing in the session used by the scheduled task.

 

What is in the connect.ini that USO AutoUpdate is using? If it has a redirect in it pointing to S:\SIMS\Connect.ini file, replace this with the actual contents of the connect.ini file in S:\SIMS and see what happens.

[CallMeMonks]

It's been years since we had USO AutoUpdate but I do remember having the same issue which was down to s:\ not existing in the session used by the scheduled task.

 

What is in the connect.ini that USO AutoUpdate is using? If it has a redirect in it pointing to S:\SIMS\Connect.ini file, replace this with the actual contents of the connect.ini file in S:\SIMS and see what happens.

The USO AutoUpdate update software is installed on the SIMS server so the connect.ini file doesn't have a redirect. It's contents includes the server name, database name etc.

[CallMeMonks]

It's been years since we had USO AutoUpdate but I do remember having the same issue which was down to s:\ not existing in the session used by the scheduled task.

 

What is in the connect.ini that USO AutoUpdate is using? If it has a redirect in it pointing to S:\SIMS\Connect.ini file, replace this with the actual contents of the connect.ini file in S:\SIMS and see what happens.

 

Thank you! Your post pointed me in the right direction and I did some further investigation. You're right, a scheduled task can't see a mapped drive. Didn't notice that within the USO configuration there is a section where you can map a drive! Sorted now.