How can i turn on debugging when trying to add a service to my VB.net app? How can i change the settings to view it remotely? I tried loading up the .asmx page in IE on that server where the file is being hosted and it just asked me to save the file-would never open it to view as a page.
That is the error i get when i try to load the .asmx file from my server.
If you copy that customerrors tag and paste it into the web config file exactly as shown, you'll get the same error screen, but it will show you a detailed error message, which should help you track down the underlying problem.
Related
I have deployed asp.net web forms website on windows server 2012 and linked with a subdomain (using Plesk panel).
Now, the website is not running any code-behind files even the Page_Load is not being called.
For testing purposes, I added the javascript alert in Page_Load; it didn't show any message, but it did show when I added alert in *.aspx file, it did show.
I didn't get the actual reason, but seems like IIS configuration error may exist.
Help me resolve the issue, will be appreciable.
Sorry for the simple question.
I have moved a site to a host by simply copying the code but even the first login page fails if I include the following :-
In Web.config file..if I add the following
or...
Aspx page..if I include a reference to a class file ( which does exist in the app_code directory )
Sign In <%If clsGeneral.str(Request("timeout")) = "t" Then Response.Write(" - YOUR SESSION EXPIRED")%>
I get the error...
Server Error in '/' Application.
Runtime 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.
etc...
Copying an application from one host to another is only simple in the file copy. There are a number of issues that may arise from the application running on the "new" server. For example, is the server running the same version of IIS? Is IIS configured properly for this application? Etc ... to see what error the application is throwing, inspect the Application Log in the event viewer on the server. This will give you some hint as to what the issue is. Without that information, there's really no place you can start, except maybe turning off the custom error or error suppression to see the error details in the browser. But I would recommend that you inspect the Application event log on the server.
I'm trying to upload a vcard file to a site i've built with ASP.NET. It's hosted on an IIS7 server.
I keep running into the "content type not allowed" error when i try to upload the file. I have write permission to the directory, I've already added the MIME type for vcards and restarted the IIS server, however it still refuses to take it.
I'm using DevExpress UploadControl and i've removed any validation from it so i am fairly certain the control is not restricting the file upload.
Any other suggestions ?
Maybe your component just allow some content types by default and new ones must be granted access manually.
Can you to debug your server side code, to see if your page code executes and to spot exactly what component are throwing up that error?
It's an HTTP error or a .net exception?
I am trying to deploy a web application to a remote server over which i have no control.
If I use FTP deployment from visual studio, I manage to get the files onto the server, but when I point my browser to the server, it gives me the standand error page:
Server Error in '/' Application.
Runtime 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 tag within a "web.config" configuration file >located in the root directory of the current web application. This tag >should then have its "mode" attribute set to "Off".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's >configuration tag to point to a custom error page URL.
I have made shure that custom errors has mode="Off" as the text above suggests. No amount of refreshing or Cntl-F5-ing gives me anything other than the error page above.
Its most likely is that the location you have put it is not setup as an IIS Application and this is required for the .net framework application to work correctly.
As you have no control on the server you won't be able to change the IIS settings, and so dropping .net onto the server isn't quite the xcopy deployment method Microsoft pushed lots.
Please verify the virtual directory is mapped to the publish location properly. Because your question tells changing the web.config has no impact.
Probably your application on remote server isn't defined as application in IIS. This means that it can't find it 'code' resources(bin or App_Code directories) and customErrors setting is taken from parent web.config.
I have a web service application which has suddenly stopped working. I have enabled directory browsing in IIS, and can view the application directory. I can view the xml files within the application directory, but I cannot view the .config files, nor can I view the wsdls of any of the web services. When I try to browse to http://server/app/service.asmx?wsdl, the browser stays in the "loading" state forever.
Any ideas what might have gone wrong here?
Have you looked in the server's event log? Many ASP.NET errors will end up there, this sounds like it might qualify
Regarding the first question about loading, are you able to browse to the site on the server?
IIS protects Web.config files by default and will typically return a "This type of page is not served" error message. This is a good thing which will keep your connection strings and what not from being casually viewed. There is more information about allowing exceptions for this here.