Quantcast
Channel: ProjectWise Design Integration Wiki
Viewing all articles
Browse latest Browse all 1890

Last Error 56049 Cannot log in to the data source. Database communication Error.

$
0
0
Current Revision posted to Project Delivery: Content Management Wiki by Thomas Hess on 8/2/2016 8:56:31 PM

 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.111
 Area: MISC
 Original Author:Arturas Zidonis, Bentley Technical Support Group

Error or Warning Message

Last Error 56049 Cannot log in to the data source. Database communication Error.

Explanation

This error message can appear logging in to ProjectWise datasource.

If you check ProjectWise services you might see that they are up and running. Trying to restart ProjectWise Integration Server service and ProejctWise Orchestration Framework service it will not start. This means that the account under which the ProjectWise processes are running, may be locked out, or that the password for this account (which by requirements should have a fixed password) has been changed.

Another possible issue is that the communication between the datasbase server and the integration server has stopped. 

How to Avoid

  1. Unlock the account or change the password back under which ProjectWise services are running.

  2. or change the account password in Services for the ProjectWise Integration Server service and ProjectWise Orchestration Framework service.
  3. On the integration server, check the ODBC connection to make sure the system is able to communicate to the database server. If that fails, then on the database server, check to make sure the database services are running.

See Also

https://communities.bentley.com/products/projectwise/content_management/w/wiki/orchestration-framework-service-will-not-start.aspx

https://communities.bentley.com/products/projectwise/content_management/w/wiki/5504.aspx

Tags: MISC, error message, ProjectWise Explorer Client, SELECTsupport

Viewing all articles
Browse latest Browse all 1890

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>