Questions and answers about OMNITRACKER ↦ System ↦ Attachments:
Verify general write access to directories "uploads" and "icons" in the installation folder "OTWG" (default:
Group "EVERYONE" must have full access to these directories.
By default the WebGateway runs under the user that is configured under "Identity" in the Application Pool (i.e. "ApplicationPoolIdentity" or "Network Service") Therefore, you have to verify general write access for this user to the "Temp" directory:
In addition, this user must have full access to these directories:
- %windir%\Documents and Settings\Default User
- %windir%\Documents and Settings\All Users
If you try to open an attachment in the WEB client, nothing happens. In OMNITRACKER Service Control Panel (
OtSvcCtl) the function
GetAttachmentInfoByKey() shows huge runtimes.
After a certain time, the Internet returns
Webseite kann nicht angezeigt werden /
The page cannot be displayed.
In order to open an attachment in the WebGW the OMNITRACKER system tries to save the attachment temporarily. Usually the file will be saved in this directory:
%windir%\Documents and Settings\Default User\Local Settings\Application Data (<- IIS6 on Windows Server 2003)
%windir%\Windows\Temp (<- IIS7 on Windows Server 2008)
Identityin the Application Pool (i.e.
Network Service) Therefore, you have to verify and adapt write access for this user accordingly.
NT AUTHORITY\NETWORK SERVICE, you have to verify write access for
NETWORK SERVICEto the appropriate directory.
Request time exceededappears when downloading attachments? How to avoid these timeouts while uploading attachments?
Request time exceeded most probably indicates that the execution timeout has been exceeded.
Increase the value of
executionTimeout in the
Web.config file in the
C:\Inetpub\Wwwroot\OTWG directory (the specified value is in seconds, default = 60).
Also compare the size of the files that are uploaded with the
maxRequestLength parameter in the Web.config file (the specified value is in KBytes, default = 4096).
You should also check the limitations in the IIS: Which value is set in IIS? =>IIS restriction of the maximum content length:
key configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength in the file
You can also add this directly in the web.config (specification in bytes!):
<requestLimits maxAllowedContentLength="134217728" />
After that, the default web site in IIS must be restarted. This must be set on all servers involved.