This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DB error + whitescreen SG 7.0

Trying to install Safeguard Enterprise 7.0 using the best practice guide.(have to because clients will be 8.1

Server is 2012 R2 with latest updates, SQL Express 2014

The page http://localhost/SGNSRV fails with error 500 and the log fills with sql 18456

Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'SafeGuard'. [CLIENT: <local machine>]

:55298


This thread was automatically locked due to age.
  • I went through the same installation over the last few days and had similar DB errors and < DBAuth>failed</DBAuth>, although I was using SQL Express 2012.

    What helped me was to re-read over the best practice on chapter 2, specifically:

    2.2 - here I created a domain user for my sql instance

    2.4 - mapped this user to the SafeGuard database with the stated permissions

    and 

    2.6 - use this user in the application pool settings as mentioned

    Hope it helps.

    Eddie

    :55309
  • Thanks Eduardo, good to hear I'm not alone. 

    I did the same thing but with a local user, I don't have a domain in this particular environment.

    I repeated the steps and reboot, same thing

    :55313
  • Is it necessary to have a domain ? I did an install on a standalone server

    :55315
  • Thanks to suppport this has been fixed. The cause 

    was WSUS.

    This can be caused by the XPress compression schema module (suscomp.dll) which gets installed with WSUS. Compression schemes are defined globally and try to load in every Application Pool. It will result in this error when the 64bit version of suscomp.dll attempts to load in an Application Pool which is running in 32bit mode [enable32BitAppOnWin64]. 32bit mode is needed for SafeGuard Enterprise Server to run.

    The solution was this.

    1. Navigate to %WINDIR%\system32\inetsrv\config\
    2. Create a backup copy of the file applicationhost.config and save it to a different location. 
    3. Open the applicationhost.config in Notepad. 
    4. Search for the following entry:

    <scheme name="xpress" doStaticCompression="false" doDynamicCompression="true" dll="C:\Windows\system32\inetsrv\suscomp.dll" staticCompressionLevel="10" dynamicCompressionLevel="0" />

    5. Remove / Disable the XPress compression schema from the configuration using the command below:

    %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

    6. Verify if the compression schema has been removed form the applicationhost.config.
    7. Save the applicationhost.config and restart IIS services.

    :55340
  • Hi Guys,

    I know its already sorted, but just wanted to let you know that there is also a Knowledge Base Article available that explains the situaiton and steps on how to resolve the issue:

    IIS 7.5 HTTP Error 500.19 in combination with WSUS and compression schema module

    Cheers,

    ChrisD

    :55347
  • Cheers, didn't find that. Might wanna add the other versions as well do(IIS 8.X and Server 2012 (R2))

    Didn't realize it had to do with WSUS at first

    :55413
  • KB has been updated with a reference to IIS 8.x and Server 2012

    Cheers,

    ChrisD

    :55421