Error situation:

This error is displayed when a user tries to login into WEB20:

"No default folder has been configured. This is mandatory for using the breadcrumb bar."

Precondition is that Web Configuration Option: Show breadcrumb bar (hide navigation tabs) is set to true, so a breadcrumb bar is used.

Solution:

A default folder has to be defined either in the Guest Login Properties (if a guestlogin is used) or a default folder has to be set via the default folder feature (File > Administration > Default Folders...)

Please refer to the OMNITRACKER Web Gateway Help. Navigation: Troubleshooting > Hints for Troubleshooting. You will find more detailed information on the individual error situations there.

You can configure the timeout in the web.config file. This file is located by default under C:\Inetpub\wwwroot\OTWG.

For more information, please refer to the WebGateway Help under Configuration file. You can find the timeout of IIS in the properties of OTWG in the IIS Manager -> Configuration -> Options -> Session timeout.

After changing these values, you should set a Execute IISreset (via Start -> Execute). Caution: This will terminate all currently active Web Sessions. In the OT-Windows client you can observe active connections as superuser via File-Administration and how long a user actually has been without server action (idle). If this value exceeds the timeout, then his session will be disconnected.

OMNITRACKER Web Gateway Help: Navigation: Configuration > Web Configurations > Guest Login Properties Window

Flag: Show Name of Guest in History and in Memo Sections

Example of an entry in the web logfile:

Performed Logout (No alive packet received within the last: 70000ms.)

If the Web Configuration option Always close Session is set to True, the following two parameters (in the Web.config or alternatively via the OMNITRACKER WebConfig Editor on the Timings tab) can be adjusted to influence the ping mechanism:

<add key="OT_PollingInterval" value="60000" />
<add key="OT_MissingPingLogoutTimer" value="70000" />

OT_PollingInterval:
Every 60000 milliseconds a network packet is sent from the browser to the web server to indicate that the web gateway is still used (i.e. the browser is not closed). Therefore, every 60 secs the page OTWNotification.aspx is called (can be seen in the network traffic).

OT_MissingPingLogoutTimer:
If the web server does not receive one of the network packets (see above) within 70000 milliseconds then the web session will be terminated immediately.

If the system has unexpected timeouts, the Web log file should be examined. Timeouts are logged here.

Example:
Performed Logout (No alive packet received within the last: 70000ms.)

The log file is activated by the following parameter in the web.config (or alternatively via the OMNITRACKER WebConfig Editor):
<add key="OT_ErrorLogDirectory" value="" />

Perform a repair installation of the WebGateway SW. Then restart the computer.

When using TabControls on web forms, only the contents of the active tab have to be transferred from the server to the client. Due to the fact that only the active tab has to be generated, the form will be rendered faster at server-side. The disadvantage is that a change to another TabControl requires a round trip. If the workflow requires input in all tabs, for instance, then this solution might be inappropriate.

As another solution, TabControls can be displayed as sections. Therefore, please use the flag Show tabs as sections in the web form editor. This has the advantage that no round trips are needed when navigating between sections. However, the complete web form has to be rendered at server-side. This can have sensible impact when the form is more complex (100-400 ms). So the amount of data, which is initially transferred from the server to the client, is much more higher, the same with other postbacks.

If the web from is more complex (complex means a lot of of OnChange scripts, script buttons, …),then it has to be decided whether TabControls or Tabs as sections have less performance impact.

Follow the notes for troubleshooting in the OMNITRACKER Web Gateway Help Navigation: Troubleshooting > Hints for Troubleshooting.

Run a repaired SW-installation of the OT WebGateway.

A detailed documentation for IIS6 (Windows Server 2003) is available here: http://support.microsoft.com/kb/299525/en-us

The usage of company certificates should be illustrated in section 2. To use public certificates, it is necessary to order the certificate from the certification authority first (e.g. Verisign, Thawte, Telekom, etc.). By usage of the newer IIS 7 (Windows Server 2008), the configuration should be identical. Only the user interface is slightly modified.

More information about II7 is available here:

http://technet.microsoft.com/de-de/library/cc771438.aspx

and

http://technet.microsoft.com/de-de/library/cc732230.aspx

After the installation of OMNITRACKER Web Gateway on a Windows Server 2008 32 Bit, the following error message pops up:

HTTP Error 500.19 - Internal Server Error.

Please verify the installation of IIS:

• Did you also install "WWW Service" and "Active Server Pages"?
• Did you install the .NET framework 2.0 and switch to the .NET folder? Did you enter "aspnet_regiis -i" there?
• IIS 7: Did you add ASP.NET 4.0 as Application Pool?

The URL to an object in the Web Client has to look like:

http:////OTWGObjForm.aspx?id=<id>&singleton=<singleton>[&guestlogin_id=<gid>][&lang=<xx>]
(OMNITRACKER Web Gateway Help: Navigation: Using the Web Gateway > Login > URLs)

You can to add the <id> of the current object with inline scripting into the message template:

http://<hostname>/<virtualroot>/OTWGObjForm.aspx?id=<%%Output ActiveRequest.UniqueId %%>&singleton=1

or alternatively - using folder=<folderpath>
The alias of the complete folder path has to be used:

http://<%%Output(ActiveSession.hostname)%%>/OTWG/Login.aspx?folder=<%%
Set folder = ActiveRequest.RequestFolder

Do
folderpath = folder.Alias & "%5C" &folderpath
Set folder = folder.ParentFolder

Loop While Not folder.IsTopFolder
folderpath = folder.Alias & "%5C" &folderpath
Output(folderpath)%%>&filterfield1=Number&filterparam1=<%%Output(ActiveRequest.UserFields("Number").Value)%%>&singleton=3&lang=en&autologin=3

The favicon.ico file is to be found in the OTWG directory and can be replaced, which is not documented separately. Note: It seems these *.ico files are cached in windows. It may be necessary to clear the cache to make the change visible.

Find an instruction here:

http://www.thewindowsclub.com/rebuild-icon-clear-thumbnail-cache-windows-10

https://support.microsoft.com/en-us/help/4050891/error-http-503-and-was-event-5189-from-web-applications-on-windows-10

Open a Command Prompt window by using the Run as administrator option. Run the following commands:

net stop WAS /y
rmdir /s /q C:\inetpub\temp\appPools
net start W3SVC

OMNITRACKER stores e-mails in the path:

%windir%\OMNINET GmbH\OMNITRACKER\EmailGatewayQueue\

The path is set in the Service Control Panel on the "Directories" tab.

If *.DAT files exist in this path, the Email Gateway will try to send them as soon as the service starts. To prevent the emails from being sent, you can simply delete them or move them to another folder.

In the control, where the plain text of the email should actually be, the email is shown as HTML-encoded text. This effect is mostly due to the fact that the text that is sent by the mail server fetched email contains ONLY an HTML part. If an email delivered as multipart message with HTML and PlainText part the OmniTracker will correctly use the PlainText part.

An Exchange server can be configured for a mailbox, that mails fetched from the Internet via POP3 are automatically ALSO be provided in PlainText format. Then a conversion is performed on the Exchange server. An extract from the Exchange manual for this configuration can be found in the appendix.