RES Software Customer Portal

To make sure the central RES PowerFuse database is back online, RES PowerFuse performs an availability check based on the settings specified in the Real Enterprise Manager under Database Setup > Database Configuration.

If the requirements have not (yet) been met, RES PowerFuse will not switch back to the central database.

Solution 1.1 - Manually redirect the computer running RES PowerFuse back to the central RES PowerFuse database
95% probability.

When the server runs in Local Fallback, but the central RES PowerFuse database is back online, it is possible to manually redirect the computer running RES PowerFuse back to the central RES PowerFuse database:

1) Stop the RES Service.

2) Rename the "pwrmenu.ini" to "pwrmenu_org.ini".

3) Rename the "pwrmenu_lfb.ini" to "pwrmenu.ini".

4)Start the RES Service.

When the service starts, the connection to the central database is made. After that, you can open the Real Enterprise Manager.

Cause 2 - The RES Service is not started
20% probability.

The RES Service is not started.

Solution 2.1 - Check RES Service settings
95% probability.

When you install RES PowerFuse 7.03 or earlier, the Real Enterprise Service will also be installed. This is an application used by RES PowerFuse that runs as a service. It is installed on Terminal Servers, workstations and laptops. The Real Enterprise Service requires a high-level administrative user account. This account must have read and write permissions to the database share.

If you want to run the service with an administrative user account, you can create a new account using Computer Management or Active Directory Users and Computers from the Administrative Tools menu (not applicable for laptop installations). For Windows 2000 or later, use Local Security Policy and Computer Management in the Administrative Tools folder to assign the local security rights to the newly created domain service account. For Windows NT or earlier, use the local User Manager to assign the local security rights to the newly created domain service account.

The following local security rights should be assigned tot the Real Enterprise Service:
1) Log on as a service.
2) Act as part of the operating system.
3) Member of the local administrators group.

The following domain security rights must be assigned:
1) Equal or higher permissions than [TechMan].
2) Citrix Administrator when using Citrix MetaFrame XP or later.

See also Knowledge Base article:
http://support.res.eu/Modules/Support/KnowledgeBaseArticle.aspx?id=1191

Cause 3

Solution 3.1 - Check DNS suffix on Terminal Server(s)
95% probability.

Check the DNS suffix on Terminal Server(s).

Cause 4 - RES PowerFuse is unable to connect to the Microsoft SQL database server
14% probability.

RES PowerFuse is unable to connect to the Microsoft SQL database server.

Solution 4.1 - Two fast ways to verify SQL connectivity with Telnet and ODBC entry
65% probability.

a) Start a command prompt on the client/Terminal Server and check if it is possible to set up a Telnet connection to the SQL Server with the command:

telnet [sqlservername] 1433

If this is successful, a Telnet prompt will be started. If not, a connection error will occur.

If the port number of the SQL-listener is changed, change 1433 to the different port number. The port number can be found in the SQL Enterprise Manager > Properties SQL Server.

b) Create an ODBC entry on the client/Terminal Server to the SQL Server.
Control Panel > Administrative Tools > Data sources (ODBC)

Client configuration: TCP/IP
Port Number: 1433 (default)

Test configuration must be OK!

Solution 4.2 - Verify the SQL Server connectivity
55% probability.

Steps to verify the SQL Server connectivity:

1) Launch SQL Query Analyzer.

2) Enter the SQL Server name.

3) Select SQL Server authentication and enter the logon name and password used for RES PowerFuse.

4) Click "OK".

5) Select the RES PowerFuse database from the drop-down list. You can find this list in the top center of SQL Query Analyzer.

6) Enter this command in the query window of SQL Query Analyzer:

SELECT * FROM tblautocount

7) Press CTRL+E to execute the query.

8) Verify that records are returned and displayed.

If any of these steps cannot be completed, the connectivity to the SQL Server is not working.

In this case, see the Knowledge Base article "Unable to connect to SQL Server Database" (http://support.res.eu/Modules/Support/KnowledgeBaseArticle.aspx?id=60).

Cause 5 - SQL server collation name of the RES PowerFuse SQL database is set to a case-sensitive collation type
12% probability.

SQL server collation name of the RES PowerFuse SQL database is set to a case-sensitive collation type.

Solution 5.1 - Change the Microsoft SQL server collation name to a case-insensitive collation type
95% probability.

Change the Microsoft SQL server collation name to a case-insensitive collation type.

You can check the collation name in the Properties window > General tab of the RES database in the SQL Console..

CI = Case Insensitive
CS = Case Sensitive

Default collation name is: SQL_Latin1_General_CP1_CI_AS

Solution 5.2 - Solved in RES PowerFuse 2008 SR4 (8.0.4.0)
5% probability.

Solved in RES PowerFuse 2008 SR4 (8.0.4.0).

Cause 6 - The database is running in single-user mode
6% probability.

When an SQL Server database runs in single-user mode, only one user can connect to the database.

Solution 6.1 - Change configuration settings for the database (SQL Enterprise Manager)
80% probability.

Change configuration settings for the database (SQL Enterprise Manager).

To change the configuration settings for a database, do the following:

1) Expand a server group and then expand a server.

2) Expand Databases, right-click the database to change and click Properties.

3) Click the Options tab and select or clear the appropriate configuration setting(s).

Solution 6.2 - Step-by-step workaround to force database out of single-user mode
72% probability.

Before following these steps, first try the other solutions!

Step-by-step workaround to force the database out of single-user mode:

1) Stop SQL Server instance.

2) Rename the database data file after you have written down the original file name.

3) Start SQL Server instance. The database will now be "Suspect".

4) Change the password of the RES PowerFuse database account after you have written down the original password.

5) Stop SQL Server instance.

6) Rename the database data file back to original.

7) Start SQL Server instance. The database will now be "Single user" (last known state of the database).

8) Take the database offline and back online again. The database will now be "Multi-user".

9) BACKUP LOG <databasename> WITH TRUNCATE_ONLY

10) Shrink the database. The database size will shrink (for example from 4.2 GB to 180 MB).

11) Prevent this problem from occuring in the future by setting transaction model to "Simple".

12) Change the password of RES PF database account back to original.

After this, RES PowerFuse will resume normal operation.

Cause 7 - A virus scanner scans all files in RES programs directory
5% probability.

A virus scanner is setup to scan all files in the RES PowerFuse / RES Workspace Manager programs directory.

Solution 7.1 - Adjust virus scanner settings
95% probability.

Scanning the RES PowerFuse / RES Workspace Manager program files directory can cause a large decrease in performance on the system. To resolve this, do the following:

Adjust the virus scanner’s filters to exclude "%Program Files%\RES PowerFuse" or "%Program Files%\RES Software\Workspace Manager"

Copyright © 1998-2011 Real Enterprise Solutions Development B.V. All rights reserved, U.S. Pat. No. "US 7,433,962", patents pending. RES, RES Workspace Manager, RES Automation Manager, the RES logo and the RES Workspace Manager Logo are registered trademarks of Real Enterprise Solutions Nederland B.V. Windows is a registered trademark of Microsoft Corporation in the United States and/or other countries. All other product names, company names, marks, logos, and symbols are trademarks of their respective owners.