Error when running a DB update to @ptitude Analyst MR3

Summary

The dbupdate.bat fails to execute fully when a “skfuser” database user password contains the special character “%”. The percent character, “%”, is used as a wild character within the batch files during dbupdate.bat execution. The failure occurs on some of the files but not all.

What happens if dbupdate.bat fails:
Some of the procedures will point to an older version of Analyst, while others are up to date on the latest version. Users will experience an inability to run some of the @ptitude Analyst features with errors occurring, or the @ptitude Analyst will crash.

If @ptitude Analyst is in debug mode, an error message will appear referencing one of the old UTC tables: e.g. error finding UTC_#

March 15, 17:20:30### DEVELOPER TRACE: 0x00000002 ==> Error - 80040e37 meaning = IDispatch error #3127 ###

March 15, 17:20:30### DEVELOPER TRACE: 0x00000002 ==> Source - Microsoft OLE DB Provider for SQL Server ###

March 15, 17:20:30### DEVELOPER TRACE: 0x00000002 ==> ADO Error: 80040e37, Invalid object name 'utc_5'.

Solution

1. Find all "skfuser" databases password and look for “%”.
2. Create a new password without using “%”.
3. Execute dbupdate.bat again.

Contacting SKF Technical Support Group

For further assistance please open a support case using the Technical Support group's self-help portal at www.skf.com/cm/tsg. Once your support case is submitted, a technician will contact you to begin working on your issue. For urgent issues we are available at these times by phone:

• Monday through Friday, 5:00 a.m. to 4 p.m. Pacific Time -
  Phone: [phone] within the US or [phone] outside the US.
• Monday through Friday, 8:00 a.m. to 4:00 p.m. Central European Time -
  Phone: [phone].
• Monday through Friday, 7:30 a.m. to 4:30 p.m. India Standard Time -
  Phone: [phone].