Software⏱️ 3 min read📅 2026-06-19

How to Fix: Administrator can run a application but produces error while a administrator previllaged user can run without error

Error occurs when admin runs application but not when admin user is privileged, related to MSSQL-2008 R2.

Quick Answer: Check SQL Server connection settings and logins for any differences between admin and privileged users.

The error 'The input string was not in correct format' occurs when an administrator attempts to run an application that is designed to run without errors as a privileged user. This issue affects administrators who are trying to use the application, while privileged users can run it without any problems. The problem arises due to the difference in how the application handles its configuration and security settings between admin and non-admin users.

This error is frustrating because it prevents administrators from performing their tasks efficiently. It's essential to identify the root cause of this issue and apply a suitable solution to resolve the problem.

⚠️ Common Causes

  • The primary reason for this error is related to the application's configuration settings. The application may be using a different configuration or setting that is not compatible with the admin user's environment. This could be due to the way the application handles its database connections, file paths, or other system resources.
  • Another possible cause of this issue is related to the SQL server settings. It's possible that the SQL server is configured in a way that affects the application's behavior when run by an admin user compared to a privileged user.

🛠️ Step-by-Step Verified Fixes

Configuring Application Settings

  1. Step 1: Step 1: Check the application's configuration settings and ensure they are compatible with the admin user's environment. This may involve reviewing the application's configuration files, registry entries, or other system resources.
  2. Step 2: Step 2: Update the application's configuration settings to match the settings used by privileged users. This may require modifying the application's code or using a different configuration file.
  3. Step 3: Step 3: Verify that the updated configuration settings are applied correctly and the application runs without errors as an admin user.

Modifying SQL Server Settings

  1. Step 1: Step 1: Check the SQL server's configuration settings and ensure they are not affecting the application's behavior when run by an admin user. This may involve reviewing the SQL server's connection strings, query optimization settings, or other system resources.
  2. Step 2: Step 2: Modify the SQL server's configuration settings to match the settings used by privileged users. This may require updating the SQL server's configuration files, registry entries, or using a different connection string.

💡 Conclusion

To resolve this issue, administrators can try configuring the application's settings and modifying the SQL server settings as described in the above steps. If the problem persists, it may be necessary to investigate further to identify the root cause of the issue and apply additional solutions.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions