<customErrors> An application error occurred on the server

Hi experts
i have a .net application that was running perfectly in my local machine, i transferd the application to the production server, but when i run the application i am getting the following error

> Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

>Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
i know that i need to add the following to web.config
     <configuration>
        <system.web>
          <customErrors mode="Off"/>    
        </system.web>
     </configuration>

Open in new window

but still not working still i am getting the same error, with no description of the error

any suggestion
thank you
LVL 1
AZZA-KHAMEESAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ronak PatelCommented:
Hi,

If only this application is hosted on your Production server then restart the IIS Service on the Production Server and try it again.

Steps:
1) Open Command Prompt as administrator.
2) type iisreset and press Enter.

If other application are also running on the same server, then don't restart the service, just open IIS Manager and select your site and on the right panel of the window in "Manage Web Site" section there is a resart button. Press it. It will reset your application.


Hope this helps.

Regards,
Ronak
0
AZZA-KHAMEESAuthor Commented:
thank you for the reply, i reset the server but still the same error
0
Ronak PatelCommented:
can you share the config file and error screen shot ?
0
CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

AZZA-KHAMEESAuthor Commented:
web.config
<?xml version="1.0"?>
<!--
  For more information on how to configure your ASP.NET application, please visit
  http://go.microsoft.com/fwlink/?LinkId=169433
  -->
<configuration>
  <connectionStrings>
    <add name="OracleDBConnectionString" connectionString="Data Source=DB;Initial Catalog=DB;User ID=testusr;Password=P@ssw0rd" providerName="System.Data.SqlClient"/>
  </connectionStrings>
  
  <system.web>
    <customErrors mode="Off"/>    
    <compilation debug="true" targetFramework="4.0">
      <assemblies>
        <add assembly="Microsoft.SqlServer.ManagedDTS, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>
        <add assembly="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
      </assemblies>
    </compilation>
    <httpRuntime/>
  </system.web>
</configuration>

Open in new window

0
AZZA-KHAMEESAuthor Commented:
and the error messageerror
0
Ronak PatelCommented:
The config file looks Ok.

Just to make sure.. please check the below items on the server:
1) Check Virtual Directory permissions.
2) Check the .Net Framework version on the server (as per your config, application will required .Net Framework 4.0).
3) Check the .Net Framework version in Application Pool. It should be .Net Framework v4.0.
4) Recycle the Application Pool.

After checking all this, still the problem persists, remove the existing site and host the web site again or contact the server administrator to check server configuration.


Hope this helps.

Regards,
Ronak
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
käµfm³d 👽Commented:
Are you certain that another web.config at a higher level isn't overriding these settings, and are you sure you've edited the correct application? The settings you have enabled are exactly what should be modified in order to get detailed descriptions from the error. If nothing else works, have your server admin remote into the production server, and bring up your page in the browser there.

Be sure to remove/disable these settings when you are done--since you say that this is a production server.
0
Vikram Singh SainiSoftware Engineer cum AD DeveloperCommented:
Hi,

1) As you mentioned that you transferred the application to production server, can you share how it was done?

2) Do you have rights or access to the production server? If yes, then please try to access the very same website from production server's browser. It will let you to see the error in that browser.

I would suggest to go as per point 2 if possible. It's the best way to look out real cause when the other way is failing.
0
AZZA-KHAMEESAuthor Commented:
hi thank you all fro the replies and sorry for the delay in response, i followed the steps mentioned by @Ronak Patel
now i am getting this error
Could not load file or assembly 'Microsoft.SqlServer.ManagedDTS, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies
0
Ronak PatelCommented:
Hi AZZA-KHAMEES,

It means your application includes a reference of Microsoft.SqlServer.ManagedDTS assembly, which might be missing in your application's bin folder.

Please make sure the Microsoft.SqlServer.ManagedDTS.dll is present in your application's bin folder.


Regards,
Ronak
0
AZZA-KHAMEESAuthor Commented:
i created a bin folder under the project that i moved to the production server, and i added the Microsoft.SqlServer.ManagedDTS.dll to it, and still i am getting the same error when i run the project from the server

Could not load file or assembly 'Microsoft.SqlServer.ManagedDTS, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
0
Ronak PatelCommented:
Hi,

Which version of MS SQL Server SSIS (SQL Server Integration Service) installed on the production server ?
It should be SQL Server SSIS 2014, because the Microsoft.SqlServer.ManagedDTS assembly version is 12.0.0.0.
So, please check the same on the server.

Also, check if the assembly is registered in GAC (Global Assembly Cache) of the server.
To check this, go to this path on the production server: C:\Windows\assembly\gac_msil\Microsoft.SqlServer.ManagedDTS


Copy that assembly into your application's bin folder (published).


Regards,
Ronak
0
AZZA-KHAMEESAuthor Commented:
sorry for the delay reply, in my application i included the reference under the bin folder and still i am getting this error
CS0234: The type or namespace name 'Dts' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?)

do i have to add the assembly to the GAC  of the production server ?
the bin folder suppose to solve this as i need to reference to it?
0
Ronak PatelCommented:
Hi,

If the MS SQL Server SSIS is installed on production server, then the assembly should be present in the GAC.

Please look into this: Can't find package Microsoft.SqlServer.Dts.Runtime for programmatic SSIS execution


Regards,
Ronak
0
AZZA-KHAMEESAuthor Commented:
its not installed, sorry for the question, but do i have to install it? why can the application refer to the dll from the bin folder only, instead of installing?
0
Ronak PatelCommented:
Okay first tell me, why do you require this assembly, I mean are you performing any data import/export operation using SSIS or any other feature of this assembly in your application?

If yes then, the SQL Server installation will be required to use this assembly members in your application.
If no then, you can simply remove its reference from your application, if it is not required at all.


Hope this helps.

Regards,
Ronak
0
AZZA-KHAMEESAuthor Commented:
Thanks, need to install sql server client tool in the server
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C#

From novice to tech pro — start learning today.