Subscribe





If you are having problems subscribing, click here.
Archives

Categories
Blog Icon

ECMPS News

Known Issue with Updating the Shared Database to the 2009 Q3 Version


Wednesday, September 30, 2009

Caution Traffic SignThere is a known issue related to updating the shared database version of the Client Tool. The issue only affects shared database users who are attempting to update from the 2009 Q2 version of the Client Tool to the 2009 Q3 version of the Client Tool. The known issue does not affect users who use a stand-alone version of the Client Tool.

Shared database updates are performed by first updating the Client Tool's shared database. This quarter, users must update their shared database from the 2009 Q2 version to the 2009 Q3 version. (Service Pack 1 for 2009 Q3 only affects the Client Tool. It does not affect the Client Tool shared database.) This is done the database administrator running a script which updates the shared database.

After the shared database has been updated, each Client Tool which connects to the shared database needs to be updated. This is where the known issue occurs. Normally, users can start up their Client Tool, log in to the EPA Host System, and then be guided through the automatic update process built in to the Client Tool. However, when users attempt to start up the Client Tool, an error occurs:

"Invalid object name 'dbo.VW_CLIENT_TOOL_SNAPINS'"

Generally, this error prevents users from continuing and updating their version of the Client Tool. In order to complete the update, shared database users should follow the steps provided on the Shared Database Update page. If the shared database has already been updated, users should only need to perform all of the steps listed under item 7. After the steps have been completed, users will have updated their version of the Client Tool to the 2009 Q3 SP1 version.

After updating to the latest version of the Client Tool, shared database users should no longer receive the error. This error only relates to the 2009 Q3 update, and the error should not occur during future updates of the Client Tool.

Labels:


0 Comments:

Post a Comment

<< Home