Troubleshooting

---

If you have any problems - unexpected error messages, incorrect report data, etc. - contact us.
To help us resolve your problem, you can submit a log file in which you reproduce the issue.

How to turn on logging mode?

Locate the appsettings.json file in the root folder of the application. Set the “DebugMode” value to “True” and specify a “DebugPath” for the log files.

  ...
  "DebugMode": "True",
  "DebugPath": "logs"
  ...

The “DebugPath” can be a relative path (e.g., “logs”) or an absolute path (e.g., “C:\ADGMWeb\logs”).

Restart the IIS web application.

You will find your log files in the specified log folder. If you used a relative path, the logs will be in the application's root directory.

Common Installation Issues

Missing ASP.NET Core Hosting Bundle

If you see an HTTP 500.19 error with error code 0x8000000d, or if the application fails to start, you may need to install the ASP.NET Core Hosting Bundle.

The application requires the ASP.NET Core Hosting Bundle matching your application's .NET version. You can download the latest version from the Microsoft .NET download page.

After installing the Hosting Bundle, restart your server or the Windows Process Activation Service (WAS).

Incorrect .NET Version

AD Group Manager Web requires .NET 8.0 or higher. If you see an error message indicating an unsupported runtime, or if the application fails to start, verify your installed .NET version:

1. Open Command Prompt as Administrator
2. Run: dotnet --info
3. Verify that you have .NET 8.0 SDK installed

If the required version is not installed, download and install it from the Microsoft .NET download page.

Application Pool Configuration Issues

Ensure your application pool is configured correctly:

1. Open IIS Manager
2. Select the application pool used by AD Group Manager Web
3. Make sure it is set to "No Managed Code" (not .NET CLR version)
4. Enable 32-bit applications should be set to "False"
5. Set the Identity to an account with proper AD permissions

Permission Issues

For the application to function correctly, ensure:

1. The application pool identity has read/write permissions to the application directory
2. The application pool identity has appropriate Active Directory permissions to read group memberships and update groups
3. The 'logs' directory (or custom path set in DebugPath) is writable by the application identity

Web.config Issues

If you're experiencing HTTP 500 errors or modules not loading properly, check that your web.config is correctly configured for ASP.NET Core hosting. The web.config should include the AspNetCoreModule or AspNetCoreModuleV2 handler.

Windows Authentication Problems

If using Windows Authentication and experiencing login issues:

1. Ensure Windows Authentication is enabled in IIS for the application
2. Make sure the "Authentication" setting in appsettings.json is set to "Windows"
3. Check that the application pool identity has proper delegation rights if crossing domain boundaries