Versions Compared

Old Version 3

changes.mady.by.user Deepankana Roy

Saved on

compared with

New Version 4

changes.mady.by.user Deepankana Roy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

SYMPTOMS

...

Requested by: Suvradip Roy   

When user is trying to import excel file in Ginesys web, an error message is showing - "HTTP Error 503. The service is unavailable".

CAUSE

...

The probable cause for the above issue is server is temporarily unavailable. If the issue persists we might notice the following error in Event Viewer logs.

Event ID 10016
“The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user IIS APPPOOL\GINESYSAppPoolFx4 SID (S-1-5-82-1358216942-634677025-1763237028-1288803088-3211383273) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.”

RESOLUTION

...

Follow the given steps to resolve the issue:

To resolve this issue we You need to provide administrative privileges to the two registry keys - CLSID & APPID. Also we need to configure the DCOM Configuration in Component Services to provide “Local Activation” permission to the users/groups of the registry keys.

This long process could be implemented quickly by running a script in Windows Powershell.

Please check the following links:
https://hinchley.net/articles/changing-dcom-security-permissions-with-powershell/

...

Please go through the following steps to resolve the issue:

  1. Open Notepad.exe.
  2. Copy and paste the following script.
  3. Save it in your disk as “Script.ps1” (Quotation marks must be included while saving in notepad).
  4. Open Windows Powershell as administrator by right-clicking on the Windows Powershell icon in Windows.
  5. Browse to the location in the disk where the .ps1 script file is saved and type ./Script.ps1 to run the command.
  6. If you get an error while running the unsigned powershell script, run the following command in Windows PowerShell to run unsigned scripts on your system and then try to run the script again.
    “Set-ExecutionPolicy RemoteSigned ”

The script is as follows:

...

take-back 'AppID\RuntimeBroker.exe'

This should resolve your issue, in case you face it again please contact our Ginesys Care portal - https://care.ginesys.in/ 

...