| #FAQ: 10036-EN, Date: 4/3/2002 When I run OroTimesheet from a "Windows NT Terminal Server Client" or "Windows 2000 Terminal Server Client", OroTimesheet cannot connect to the database. |
| The information in this article applies to : OroTimesheet 4.x (English) OroTimesheet 4.x (French) Description When you install OroTimesheet 4 on a Windows NT 4 Terminal Server or Windows 2000 Terminal Server and OroTimesheet is configured to access the database locally (From the connections manager, the "The database is located" option is set to "On my local computer"), OroTimesheet runs fine from the server console but cannot access the database when ran from a "Terminal Server Client". Solution If you want to run OroTimesheet from a "Terminal Server Client", you need to configure (with the "Connections manager" utility) OroTimesheet on your server to access the database in "Remote server" mode instead of local mode. You need to do that even if the database is located locally on the server.
If you use the TCP/IP protocol, you can type "localhost" as server name. Type the Windows server name if you use the NetBEUI protocol. Whatever the protocol used, you don't need to change the "Full path name to the database" field. Status Information |
| © 1996-2008 OroLogic Inc. |