Knowledgebase

Possible Reason: The 'ASP.NET Impersonation' is enabled for the site. This is an known problem on Windows Server 2012. Please disable the 'ASP.NET Impersonation':

1. Start the IIS-Manager.
2. Navigate to the site of the SpaceObServer Web Access
3. In the middle pane, in section IIS choose 'Authentication'.
4. Deactivate the 'ASP.NET Impersonation'.
5. Restart the site.

Possible Reason: ASP.NET 4.7.2 has not been enabled in the 'Windows Features' underneath the 'Internet Information Service (IIS)'. This is an known issue on Windows Server 2012. Please activate ASP.NET 4.7.2 in the 'Windows Features' underneath the entry 'Internet Information Service (IIS)':

1. Open the Server Manager.
2. On the dashboard use the entry 'Add Roles And Features'.
3. Click on 'Server Selection'.
4. Click on 'Server Roles'.
5. Navigate to 'Web Server (IIS)' > 'Web Server' > 'Application Development' and activate 'ASP.NET 4.7.2'.
6. In the next dialog all dependend features will be shown. Press 'Add Features'.
7. After the installation press the button 'Close' and try to execute the SpaceObServer Web Access in the browser again.

A possible Reason: The HTTP-Feature is not enabled in the .NET Framework 4.7.2. Please activate the Windows Feature "HTTP Activation". Execute the SpaceObServer Web Access setup an press 'Repair'. The setup installs the feature automatically.

Alternatively use the manual steps via  the Server Manager:

1. Open the Server Manager.
2. On the dashboard use the entry 'Add Roles And Features'.
3. Go to 'Server Selection'.
4. Go to features and navigate to '.NET Framework 4.5 Features' > '.NET Framework 4.7.2' > 'WCF Services' and enable the 'HTTP Activation'.
5. Click on 'Next' until the Button 'Install' appears. Enable the checkbox 'Restart the destination server automatically if required' and press 'Install'.
6. After the installation press the button 'Close' and try to execute the SpaceObServer Web Access in the browser again.

The logged in user has no read permission to query his groups from the Active Directory. The group 'Authenticated Users' has no read permission. Grant read permission to the group 'Authenticated Users' of the affected user:

1. Open Admin.msc.
2. Go to the Active Directory.
3. Search for the affected user and open his properties.
4. In the tab 'Security' select the group 'Authenticated Users'.
5. Enable the checkbox 'Read' and press 'Apply'.

Possible Reason 1: The 'ASP.NET Impersonation' is enabled for the site.

Solution: Disable the 'ASP.NET Impersonation':

1. Start the IIS-Manager.
2. Navigate to the site of the SpaceObServer Web Access
3. In the middle pane, in section IIS choose 'Authentication'.
4. Deactivate the 'ASP.NET Impersonation'.
5. Restart the site.

Possible Reason 2: The web service tried loading a 64 bit DLL. This is however not possible, since the 'Application Pool' of the SpaceObServer web service is configured to run 32 bit Applications only.

Solution: We have to prevent loading 64 bit DLLs:

1. Open a command line prompt with Administrator permissions.
2. Execute: IISRESET /STOP
3. Open the file "applicationHost.config" in "C:\Windows\System32\inetsrv\config".
4. Search for tags named "<add>" and "<filter>" matching the DLL, e.g.:
   
   <add path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll" allowed="true" groupId="MSExchangeClientAccess" description="Microsoft Exchange-Clientzugriffsserver" /> <filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll" enabled="true" />
5. Add the attribute preCondition="bitness64" to these tags, e.g.:
   
   <add path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll" allowed="true" groupId="MSExchangeClientAccess" description="Microsoft Exchange-Clientzugriffsserver" preCondition="bitness64" /> <filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll" enabled="true" preCondition="bitness64" />
6. Save the file.
7. Execute: IISRESET /START

In that case mostly the .NET-Framework 4.7.2 is not installed and the system has ignored the requirement in the setup. Please install the .NET-Framework 4.7.2:

1. Open the browser an go to Microsoft´s download page.
2. Download and install the .NET-Framework 4.7.2.
3. Try to open the SpaceObServer Web Access in your browser again.

The physical path is invalid. Set the physical path of the website to the installation folder of SpaceObServer Web Access:

1. Start the IIS-Manager (inetmgr).
2. In the left pane, navigate to Sites > SpaceObServer Web Access.
3. In the right pane, select 'Advanced Settings'.
4. Set the value of the 'Physical Path' to the installation path of SpaceObServer Web Access. The installation path is 'C:\Program Files\JAM Software\SpaceObServer Web Access' by default.
5. A restart of the website or a 'recycle' of the application pool is not required. Just open SpaceObServer Web Access in the browser again.

Possible Reason 1: The Forms Authentication is not enabled in the 'Windows Features' or not enabled in the IIS-Manager for the web site.

Solution: Activate the 'Forms Authentication' in the 'Windows Features'.

Possible Reason 2: No "SpaceObServer Enterprise Edition" or "SpaceObServer Remote Client" is installed on the server.

Solution: The SpaceObServer SpaceObServer Web Access requires an installed "SpaceObServer Enterprise Edition" or "SpaceObServer Remote Client".

Possible Reason 3: The 'Application Pool' has insufficient access permissions.

Solution: Change the identity of the 'Application Pool':

1. Execute on the windows console: C:\Windows\System32>C:\Windows/System32/inetsrv/appcmd set config /section:applicationPools /[name='spaceobserver_apppool'].processModel.identityType:ApplicationPoolIdentity
2. It was successful, if the following Message comes up: "Applied configuration changes [...]".

Alternate steps:

1. Run 'Internet Information Services (IIS) Manager' (Press Windows-Key and Type 'IIS Manager') .
2. In the 'Connections' navigate to 'Application Pools', select 'spaceobserver_apppool' and click on the link 'Advanced Settings'.
3. In the section 'Process Model' set the attribute 'Identity' to 'ApplicationpoolIdentity' and press 'OK'.
4. Stop and start the 'Application Pool' 'spaceobserver_apppool'.
5. Try to start the SpaceObServer Web Access in the browser again.

Possible Reason 4: The Firewall blocks requests to the Internet Information Service (IIS).

Solution: Enable the rule in the firewall for the IIS:

1. Open the firewall settings
2. Select 'Inbound Rules'
3. Scroll down to 'World Wide Web Services' and open the context menu
4. Select 'Enable Rule' via the context menu:

Possible Reason 5: Some cookie values are invalid.

Solution: Delete application cookies from your browser:

1. In Internet Explorer Press Strg + Shift + Entf
2. Activate Checkbox "Cookies and Websitedata"
3. Press Button Delete
4. Press F5

The connection to SpaceObServer.exe is not registered for OLE in the system. Use the following steps to register the SpaceObServer:

1. Logout from the SpaceObServer Web Access.
2. Execute the following command on the windows console (as Administrator): C:\Program Files\JAM Software\SpaceObServer Web Access\bin\SpaceObServer.exe /regserver
3. Login into the SpaceObServer Web Access.

You are accessing the SpaceObServer Web Access via "https" protocol, but there is no valid SSL (Secure Sockets Layer) certificate installed

You can proceed without valid certificate. To do so just click "Continue to this website (not recommended)".
To resolve the certificate issue you have to install a valid SSL certificate. We do not provide detailed steps how to install the certificate here.