1. Error connecting to Oracle Database
Problem:
When executing the following Opus query built in the Opus Query Builder on the Oracle Database: SELECT [EMPLOYEE_VIEW].[EMPLOYEE_ID], [EMPLOYEE_VIEW].[LAST_NAME], [EMPLOYEE_VIEW].[FIRST_NAME], [EMPLOYEE_VIEW].[GENDER],  the following error message is returned:[EMPLOYEE_VIEW].[DATE_OF_BIRTH], [EMPLOYEE_VIEW].[YEARS_SERVICE] FROM [EMPLOYEE_VIEW] WHERE  ORA-00936 - Missing expression.

Solution:
Remove the square brackets [] from Oracle data source.

2. Sharing folders for MS Access files

Problem and Solution:
When sharing a folder to access an mdb database file, if the user Everyone is used with Read or Full permissions then any user attempting to connect to the same mdb database file in that folder can connect. If Authenticated Users is used with Read permissions then any user attempting to connect to the same mdb database file in that folder can also connect, but if Authenticated Users is used with Full permissions then only users attempting to connect with the same username and password as the first user that connected to the same mdb database file in the same folder can connect.

3. Error fetching data – column size too large

Problem:
If the following error description is displayed in the OPUS web page when generating a Data Grouping report then the size of the fields that the grouping is done on, is too large: Error fetching data: Relate, Compute By, and Sort operations cannot be performed on column(s) whose defined size is unknown or too large.

Solution:
This is only a problem with Microsoft SQL Server, Oracle seems to work fine. It is recommended that if for example you are doing grouping on two fields, that the defined size of these two fields in the design of the table in SQL doesn't exceed 2000.

Problem:
When opening the Network Browsing dialog while creating a new datasource, the section that is meant to display the available domains and computers on the Network is empty.

Solution:
Check the user details in OPUS Setup for the Network Share Username and Password by simply clicking the Apply button.

4. Error fetching data – column size too large

Problem:
If the following error description is displayed in the OPUS web page when generating a Data Grouping report then the size of the fields that the grouping is done on, is too large: Error fetching data: Relate, Compute By, and Sort operations cannot be performed on column(s) whose defined size is unknown or too large.

Solution:
This is only a problem with Microsoft SQL Server, Oracle seems to work fine. It is recommended that if for example you are doing grouping on two fields, that the defined size of these two fields in the design of the table in SQL doesn't exceed 2000.

5. Blank Excel Datasource worksheet

Problem:
When attempting to view the worksheets of your Excel datasource in the OPUS Configurator you find that the worksheet displayed is blank.

Solution:
This means that there are links on one of the worksheets that is invalid, meaning that the source of the link does not exist. Remove or update the source link appropriately

6. Connecting to an Access database

Problem and Solution:
When Adroit logs data to a Microsoft Access database file it creates a lock file (LDB). Now if OPUS connects to this file after Adroit has to log data, and the folder is shared with READ-ONLY, then OPUS will not be able to connect because it can not edit the LDB file in a READ-ONLY directory. So the Share Folder containing the Access database must be set to FULL CONTROL for OPUS to also connect after Adroit has. If OPUS connects first you don't have this problem because OPUS connects in a READ-ONLY state and therefore doesn't need to create a lock file. It is also important to remember that Adroit connects to a local file through C:\ path where OPUS connects through the Shared Folder.

7. Register the Adroit MISSRVR.exe

Problem and Solution:
If the normal way of registering the Adroit MIS Server, which is by simply running the MIS server application from the computer that has Adroit installed, doesn't work to enable the OPUS Configurator to open the Adroit datasource client then it might be necessary to copy the MISSRVR.exe locally with it's relevant dll's and register it locally by running the now local copy MISSRVR.exe.

8. Cannot connect to Adroit Agent Server

Problem and Solution:
OPUS cannot connect to my Adroit Agent Server. If OPUS is NOT installed on the same computer as the Adroit Agent Server, then the Adroit Agent Server’s license requires a remote node license in order for OPUS to connect to it.

9. Error: The group name could not be found

Problem:
The error, the group name could not be found, is sometimes generated when attempting to connect to Access database or Excel file on another computer when using the browsing dialog in the OPUS Configurator resulting in the user not being able to open the directory containing the desired file. This error is very rare and we have not yet been able to find the reason why this occurs.

Solution:
As a temporary solution, browse to the desired file using Windows Explorer; copy the network path to the file including the filename and paste it into the Selected Path textbox on the Choose Datasource page of the datasource wizard. Then after the new datasource connection has been created, edit the connection, select the Advanced button and enter the correct authentication details to connect to the configured resource

10. Link Tables in Access datasource not connecting

Problem:
Access databases have the functionality to configure a link table to a table in another Access database. This source database can reside on the same computer as the master database or on a remote computer. If the source database resides on a remote computer then an OPUS datasource using the master Access database can’t make a connection to that source database.

Solution:
There are two things you’ll need to do to enable this connection using the OPUS datasource (N.B. must be logged on to the computer as an administrator user):   1.    Open the Component Services application under Administrative Tools. Browse to the OPUS Server application under Console Rootà Component Services à Computers à My Computer à COM+ Applications. Right-click the OPUS Server application and select Properties. Select the Activation tab and select the Library application option. Click Ok on all pop up dialogs and click Apply to close the OPUS Server Properties window. 2.    Stop the OPUS Server from the OPUS Service Manager task-tray icon. Open Windows Explorer and browse to the \OPUS\Server install directory. Double-click the OPUSServer.exe file which will run this application as the logged on and not as a service.

11. ODBC--connection to 'SQLServerName' failed

Problem:
When attempting to retrieve data in the OPUS Configurator from a link table in an Access database that links to a SQL table on a remote SQL Server database, the error ODBC--connection to 'SQLServerName' failed is generated. Adding the new link table from an ODBC Data Source in Access was successful and the data from SQL can be viewed in MS Access after the link was created but still an error is generated in OPUS when attempting to retrieve the data.

Solution:
Follow these steps to resolve the error:
1.      Close the OPUS Configurator and restart the OPUS Server so that the connection from OPUS to the Access database can be cleared.
2.      Now delete the current link table that is generating the error because the connection details can’t be edited.
3.      Recreate the link table but now when you select the required table from the list of available tables also select the Save Password option before clicking Ok.

12. When you query through a view that uses the ORDER BY clause in SQL Server 2005, the result is still returned in random order

Problem:
Creating a view in SQL 2005 that uses the ORDER BY clause to return data in a specific order, returns a result to OPUS in random order. However, this behavior is different in Microsoft SQL Server 2000. In SQL Server 2000, the result is returned in the order that is specified in the ORDER BY clause.

Solution:
Apply the hot-fix below to the SQL Server where the OPUSDB resides. This is a known problem with SQL Server 2005; follow this link to http://support.microsoft.com/kb/926292 to download the available hot-fix on the Microsoft website for SQL Server 2005 and follow the section Actions after you apply this hot-fix. N.B. Apply the action list to the master database on the SQL Server where the OPUSDB resides.

13. Using a Stored Procedure to get data from an InSQL view fails

Problem:
Creating a SQL Stored Procedure that contains a query to retrieve data from an InSQL view and attempting to access this SP in the OPUS Configurator to display a list of return fields, fails and displays an error. Executing this SP from the OPUS Query Builder executes perfectly and returns the available data but attempting to view the available return fields in the OPUS Configurator displays an error.

Solution (for advanced users only):
Follow these steps to use the SP return fields on a report element: 1.    Modify the query in SP to also perform an INTO to create a new table and insert the resulting rows of data from the query into it. For the name of the table being created, use unique name that won’t be duplicated. This table operates like a temp table. 2.    At the beginning of the SP do a check if the temp table being created in the query already exists and drop the table if true. 3.    Execute the modified SP from Query Analyzer to ensure that the temp table gets created every time the SP is executed. 5.    Create the required report from the new SP return fields and test it to ensure that data is returned from the SP when the report is generated. 6.    Modify the new SP to first call the original SP before querying the temp table. This is to ensure that the newest data is always retrieved when executing the report. VERY IMORTANT: Only do this step after the report has been successfully created and tested

Cause:
The actual cause is not know but it has been established that only an InSQL view used in a Stored Procedure causes this type of error when attempting to view the available return fields.

14. Stored Procedures not returning field list

Problem:
When select a Stored Procedure (SP) in the OPUS Configurator to display a list of return field, this list only displays @RETURN_VALUE. But when the SP is executed in SQL Management Studio then it runs successfully and returns all the required fields. This problem was only discovered on a SQL datasource that was using the new Connection String format implemented in OPUS to support VISTA/WINSERVER2008 because the old Connection String format is not supported by VISTA/WINSERVER2008.

Solution:
The SQL Transact property SET NOCOUNT ON must be inserted at the top of the problem SP to cause the field names to be returned. SET NOCOUNT ON will prevent messages generated by embedded queries from interfering with the final result set of the Stored Procedure; which didn’t seem to be a problem when using the old Connection String format.

15. Can’t retrieve SQL database list on Polish XP

Problem:
When attempting to configure a new OleDB datasource to a database on a SQL Server, viewing the database list for the selected SQL Server fails and therefore stops the user from completing a successful configuration of a new OleDB datasource.

Solution:
The OPUS Server install has now implemented a new registry key call ConnectionMode under ODBC which allows users to specify an alternative method for retrieving a SQL Server database list. Currently two value options are supported when using the ConnectionMode registry key:
1.    0 – This is also the default if no registry key exists, uses the SQLSetConnectOption and SQLBrowseConnect API function calls.
2.    1 - Uses the ADODB object. This is to connect to a SQL Server from a Polish operating system

16. Connect to remote SQL fails with NT Authentication

Problem:
Attempting to connect to a remote SQL Server using NT Authentication while creating an OleDB datasource in the OPUS Configurator fails and returns an error: The Current Windows user does not have access to this SQL Server. If SQL Authentication is used then the connection is successful. And using the OPUS OleDB Test Client also works fine when using NT Authentication.

Solution:
Update the “Network Share User name” in OPUS Setup to a domain user, such as the logged on user, which does have sufficient access rights for network resources.

Cause:
The above mentioned symptoms are a result of an incorrect “Network Share User name” specified in OPUS Setup. The user details specified are probably that of a local user, which would not have sufficient rights to access a network resource such as a remote SQL Server.