1. IIS users disabled

Problem and solution:
If the IUSR_ and IWAM_ users are disabled under your Windows User Account settings, then IIS (Internet Information Services) will not work and therefore connections between the OPUS client’s and server will not be established.

2. Remote client connection fails

Problem and Solution:
When attempting to connect to a remote OPUS Server through an OPUS web page client in Internet Explorer, it is important to ensure that the username and password specified for the directory security of the OPUS Virtual directory on the OPUS Server computer is correct. If the user details are incorrect then a remote client attempting to connect to the OPUS Server will fail. But if the authentication details have been set up correctly on the OPUS Server computer and a remote client still can't connect then the remote client computer must use the IP address of the OPUS Server in the URL to connect.

3. Error page when opening OPUS web page client

Problem and Solution:
When starting an OPUS Server computer that does not have a network, but has the Microsoft Loopback Adapter installed, you must ensure that Skype is not running at startup. If Skype is running when the computer is restarted with the Loopback Adapter also running.

4. Connection to OPUS Server through a Firewall fails

Problem and Solution:
If you want to connect to an OPUS Server through the OPUS web page client in Internet Explorer from a remote computer with the Firewall on the OPUS Server still enabled, then you have add inetinfo.exe application to the Firewall Exceptions list.

Select All option in OPUS Query
The '* (All)' option selected from a Datasource parameter drop down list is not applicable in OPUS Queries because it causes that the SQL statement to become invalid. A fix to modify the SQL statement to handle the ‘* (All)’ option to return all values for a specific field.

5. Formatting Functoid in a parameter

Problem:
If you require displaying a date time value on a report, which was created in a functoid and then dragged into a parameter, you might notice that the output value displayed on the report is the incorrect format. This problem is specific to OPUS Server configurations that are running as a service under Local System Account, even though the logged on user has the correct date time format specified under Regional Settings.

Solution:
To set the date format for the Local System Account you will need to modify the registry as follows (P.S. Adroit Technologies takes no responsibility for any undesired effects caused by modifying the registry):
1.        Select Start à Run and type in regedit and click Ok.

After updating the sShortDate registry value to the desired format, restart the OPUS Server before running the report in question.

6. Emailed Schedules failing

Problem and Solution:
If you have the following error message logged in the Scheduler.log file,
(5/4/2006 5:00:41 PM -2147418113 MailReport: The message was undeliverable. All servers failed to receive the message: This e-mail address is being protected from spambots. You need JavaScript enabled to view it ,)

Scheduled Printing

Problem and Solution:
If you would like to schedule a report to print or schedule to save to PDF or HTM or schedule to e-mail in PDF or HTM format, you will need to change the Log On User Account for the

OPUS Server service from Local System Account user to a valid Windows user. The reason for this is that the Local System Account does not have access to printers on the operating system. Consider to following solutions:
- Either run the OPUS Server as an application by simply double-clicking on the OPUSServer.exe file in the …\OPUS\Server directory. The disadvantage of this method is that if the computer restarts automatically after a power failure then the printing schedules won’t execute because the OPUS Server service will run as the Local System Account.
- Or run the OPUS Setup from the Start menu, Programs, OPUS and select the Change the OPUS Server Log on User Account option to configure a valid Windows user.
- Browsing Network Printers
- Windows user. The Local System Account does not have access rights to network printers on the computer and therefore a valid windows user must be configured for the OPUS Server service.

7. Cannot set margins for PDF

Problem:
When configuring a schedule to save or email a report in PDF, the page margins are incorrect can’t be configured accordingly to adjust the page size. Even if the page margins are adjusted in Internet Explorer, the schedule always generates a PDF with the same margins.

Solution:
Firstly it is important to remember that by default the OPUS Server service it set to run as the Local System Account which allows the OPUS Server to still generate reports even if a user has not logged onto the server PC. Therefore the Local System Account is not linked to any logged on user and its printer settings are not updated when the page margins are adjusted in Internet Explorer.

To set the page margins for the Local System Account you will need to modify the registry as follows (P.S. Adroit Technologies takes no responsibility for any undesired effects caused by modifying the registry):

8. Cannot set PaperSize for PDF

Problem:
As with the previous problem with setting margins, the PaperSize setting may also need to be configured for Scheduling to PDF.

Solution:
Firstly it is important to remember that by default the OPUS Server service it set to run as the Local System Account which allows the OPUS Server to still generate reports even if a user has not logged onto the server PC. Therefore the Local System Account is not linked to any logged on user and its printer settings are not updated when the PaperSize is adjusted in Internet Explorer.

To set the PaperSize for the Local System Account you will need to modify the registry as follows (P.S. Adroit Technologies takes no responsibility for any undesired effects caused by modifying the registry):
1.        Select Start à Run and type in regedit and click Ok.
2.        Browse to: HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\Internet Settings.
3.        Add a new DWORD value called PaperSize with one of the following numeric values:
i.      1 = Letter
ii.      5 = Legal
iii.      9 = A4
iv.      13 = B5

9. Using active browser to open OPUS web page

Problem:
If you have your Internet Explorer browser open to a web site, let’s say to www.google.com and then launch the Opus web page, instead of opening a new Internet Explorer browser for the Opus web page, the Windows operating system uses the existing active Internet Explorer browser instead.

Solution:
In Internet Explorer à Tools à Internet Options à Advanced, uncheck 'Reuse windows for launching shortcuts'. (Internet Explorer 6)

10. To run OPUS on 64-bit Windows 2003 (IIS 6.0)

Problem:
The OPUS web client and the OPUS Configurator does not connect to the OPUS Server after installing on Windows Server 2003 64-bit operating system. N.B.: This does NOT apply to Windows Server 2008 or VISTA.

Solution:
To enable IIS 6.0 to run 32-bit Web applications on 64-bit Windows, follow these steps:
1. Open a command prompt and navigate to the %windir%\Inetpub\AdminScripts directory.
2. Type the following:
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true
3. Press ENTER.
4. And follow this link for further information: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/0aafb9a0-1b1c-4a39-ac9a-994adc902485.mspx?mfr=true