1. OPUS Server service does not startup

Problem:
On some Windows installs the OPUS Server service doesn't startup with Windows Auto logon.

Solution:
When the operating system starts up, all Windows Services start as well and because the OPUS Server is attempting to startup before the SQL Server has started up a connection to the OPUS database can’t be established. The sequence of Services starting up is controlled by the operating system. Set the OPUS Server service dependant on SQL Server.

Large numbers
The OPUS Server processing engine is not designed to process numbers larger than 1.82689E+308.


2. Connection to SQL through a Firewall fails

Problem and Solution:
When attempting to connect to a remote SQL Server in the Change the OPUS Database option in OPUS Setup, the OleDB Test Client or by simply creating a SQL datasource connection in the OPUS Configurator, which is on a computer with an enabled Firewall, it is not sufficient to add the SQL Server Port.

Problem:
When a PC is restarted, the OPUS Server fails to start because the SQL Server on the PC hasn’t started in time. If the OPUS Server is connecting a local SQL Server then the OPUS Server is dependant on the SQL Server starting up first so that a successful connection can be made.

Solution:
Configure the local SQL Server service as a dependency for the OPUS Server service:
- Open the Registry Editor; go Start à Run, type ‘regedit’ and click Ok.
- Browse to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services \OPUS Server.
Add a new registry key under OPUS Server called DependOnService as a Multi-String Value by righting-clicking in the right-hand pane and selecting
- à Multi-String Value and type in DependOnService.
- Once the DependOnService key has been created, double-click this key and enter one of the following values:
·         If the OPUS SQL Backend was installed then enter MSSQL$OPUS.
·         If the Microsoft SQL 2000 was installed then enter MSSQLSERVER.
- Click Ok and verify that the DependOnService key now displays the relevant data value.

Restart the PC to ensure that this configuration was applied successfully

3. Invalid username or password error (#1)

Problem:
After uninstalling SQL 6.5, OPUS Setup fails to install COM+ components displaying the Invalid username or password error. When attempting to view COM+ components in Component Services under Administrative Tools, the following error is displayed: DTC was installed by the SQL server. Please Reinstall! So then COM+ is not at all accessible and hence why OPUS Setup can’t install the OPUS components and therefore the Server install can’t be completed.

Solution:
MSDTC needs to be reinstalled. To reinstall follow these steps:
1. Start à Run à type in msdtc –uninstall.
2. Delete the HKeyLocalMachine\Software\Microsoft\MSDTC registry key.
3. Start à Run à type in msdtc –install.
4. Restart the PC.
5. Run OPUS Setup and complete the Server installation.
Please note: reinstalling MSDTC will loose all the information about the current pending transactions.

 

4. Invalid username or password error (#2)

Invalid Problem:
When attempting to apply the Network Access User details during the OPUS Server installation, an username or password error is displayed even if the user details are correctly entered. Also when attempting to access the COM+ Applications folder in Component Services under Administrative Tools, an error is displayed and the COM+ Applications are not accessible. COM+ is not accessible and hence why OPUS Setup can’t install the OPUS components and therefore the Server install can’t be completed.

5. SQL Backend install freezes

Problem and solution:
The OPUS Server installation has the option to install a SQL MSDE or SQL Express Backend if the user does not already have SQL installed. Connecting to a SQL database is compulsory for the OPUS Server to manage the OPUS framework. Sometimes the SQL Backend installation freezes and does not complete. If the install process freezes for a couple of minutes without any noticeable change, then try the following solution:
Open the Windows Task Manager.

6. Slow connection to OPUS Server

Problem:
The initial problem which is very apparent to users when logging in to the OPUS Configurator is that the log in time, which usually only takes a few seconds, now takes a few minutes. The log in through is successful but simply just takes a few minutes.

Solution:
Each function call through MSSOAP is being intercepted by ISA Client which is causing the delay. So either upgrade your version of ISA Client or uninstall it.

Causes:
The communication layer between the Configurator and Server is handled by MSSOAP (Microsoft Simple Object Access Protocol). The cause of the delayed log in time in due to the fact the every function call made between the Configurator and Server through MSSOAP takes approximately 23 seconds to complete with 10 to 15 function calls required during the log in process.