Search results matching tag 'debugging'

IIS7 don't access a .dll

mathiasruck — Wed, 18 Feb 2009 21:11:48 GMT

Hi all,

I have IIS7 and Analisys Server on Windows Server 2008 working, but I only have access to a dll (msmdpump.dll) on localhost (other filetypes funct properly). if I try to access msmdpump.dll from another host, I get the error:

"500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed."

Anyone had this error?

Sorry my bad english, Thank's.

IIS7 Client Side Debugging Problem - Solved

HakanSonmez — Fri, 16 Jan 2009 11:27:54 GMT

I found the solution just after posted this message. Anybody has this issue continue reading.

1- Push Win+R buttons and execute Run window

2- Copy/Paste this :

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpErrors -errorMode:Detailed

Push enter button and thats all.

Many thanks to anilr for his help. This solve is not belongs to me it s anilr's.

Problem was below:

System: IIS7 running on Windows Server 2008 OS

Hello,

I hava a big problem and cant solve anyway. I have searched for days and find some topics about it also in iis.net but any of them can be solved my problem. I cant understand what is wrong.

I am attaching screenshots, please help me. Many thanks for helpers

Server side explorer page:

Client side explorer page:

ASP Config:

Breakpoints are not hitted correctly when debugging classic ASP on IIS 7.0

Rudidlo — Tue, 23 Dec 2008 13:10:08 GMT

I have several projects wroted as classic ASP 3.0 pages. I changed my OS to Windows Vista last month. I'm not able to debug classic asp pages with Visual Studio 2005. I'm able to attach worker process, but when exception is elevated or breakpoint is hit, Visual Studio places cursor to another line of code.

Than you for any valuable advice,

No Useful Error Messages Appear

Gary Dahl — Fri, 19 Dec 2008 17:13:14 GMT

Hello,

We don't have any useful error messages appearing with classic ASP and IIS 7. We're trying to have errors with line numbers and specific codes for debugging purposes.

Errors on my local browser are all "500 - Internal Server error". The same error on the server is "HTTP 500 the website cannot display the page".

In IIS, Calculate line numbers, Enable Client-side debugging, Enable Server-side debugging and send errors to browser are all set to true. In my IE, Disable Script Debugging is unchecked. Show friendly error messages, has been tried off and on.

We've spent days on this to no avail. Any help would be greatly appreciated.

Gary

Http 500 - Internal Server Error

goelira — Mon, 03 Nov 2008 20:09:34 GMT

I am using classic ASP to browse my site. I have a page 'neighbors.asp' from which onsubmit event I need to send a mail. I have created a script page 'sendmail.asp' for coding the mail and set this as an action on neighbors.asp

Once I fill all details on neighbors.asp and click on submit, I receive the following error:

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

When I have disabled "Show friendly Http Errors" from Internet Options, I got the following msg:

An error occurred on the server when processing the URL. Please contact the system administrator.

FastCGI/Perl/IIS debugging nightmare with error -2147467259

morungos — Wed, 29 Oct 2008 19:27:37 GMT

I've been working for days trying to get a Catalyst-based Perl application running under FastCGI/IIS. So far, it seems like a total black box. I know it is possible, as a trivial FCGI script works OK - the question is: all the error I ever get, no matter what else I try, is:

Error Details:

The FastCGI process exited unexpectedly
Error Number: -2147467259 (0x80004005).
Error Description: Unspecified error

This is not particularly helpful. There are about a million possible problems, many but not all involving permissions. The same app works fine under CGI, but we really need the performance of FastCGI - PerlIS is not an option as we need better caching than just caching the interpreter, and ActivePerl has unresolved memory leaks too. We have a good Perl, and all works well until we try to get it working with IIS. Also, the Catalyst FastCGI script appears to work just fine under the command line.

What I could really use is some tricks to get some kind of error message out of FastCGI. Any kind of error message other than the above will do. Is there any way of persuading IIS to give me a bit more feedback? We're using IIS6, Perl 5.10 (several different builds, same problems). The framework is Catalyst and I know this is likely an issue - but I cannot find how without some debugging feedback of some kind.

Any help would be very welcome. FastCGI seems perfect in principle, but deployment is currently a non-starter

VS2008 debugging problems

CrispinH — Sat, 20 Sep 2008 21:59:29 GMT

I'm attempting to debug VB ASP.NET websites within IIS7 using VS2008 SP1 on Vista 64-bit Ultimate but getting the message "Unable to start debugging on the web server. IIS does not list a web site that matches the launched URL".

The next test was to run the website using the file system rather than IIS – that works, so it looks like an IIS7 config setting that is the problem.

So next I ran:
%systemroot%\system32\inetsrv\APPCMD list sites
To see if my test site was present – and it is.

I'm reasonably sure that debugging has worked in the past, but can't be absolutely sure because I've been doing WinForms stuff recently and websites on a Windows XP using VS2005 but not websites on Vista using VS2008. However for the Vista/VS2008 development I have installed .NET Framework 3.5 SP1 - so that may be a factor. Also I’ve installed the URL Rewrite module (though I did remove it temporarily whilst having these problems).

Apart from that I've done all the usual things like run in Administrator mode, enabled Windows Authentication, HTTP Keep Alives are enabled per http://ryanfarley.com/blog/archive/2005/08/23/8540.aspx.

The developer learning page at http://learn.iis.net/page.aspx/387/using-visual-studio-2008-with-iis-70/ goes through creating a website with VS2008 but this didn’t bring me any nearer a solution.

The page at http://msdn.microsoft.com/en-us/library/dwesw3ee(VS.80).aspx does not cover Vista and VS2008 (at this time) and there appear to be some material differences.

On VS2003 there used to be a webinfo file that ensured that the debugger could reference the project file, but that now seems obsolete.

What magic setting will finally persuade VS 2008 to start debugging these VB ASP.NET sites?

TIA

Crispin

ASP Detailed Error Messages

Dotren — Wed, 21 May 2008 20:47:01 GMT

Greetings,

I've got a IIS7.0 web server on our local network here at my office and I'm using it to learn Server 2008 and IIS7 features along with testing our new company website before we push it live.

I was doing some ASP the other day and noticed I could not get the older styled detailed error messages to appear. Even after making sure Send Errors to Browser was turned on I still only got the default error message to appear on the box I was using to access the website.

So far, the only instance where I've gotten the detailed error messages to appears if I accessed the webpage from on the server itself.

I understand the security issues here and really its not a huge deal to remote onto the web server and run my classic ASP on the server's browser but now I'm curious if there is a setting to allow it to send detailed error messages to remote clients?

Thanks!
Jason

Server.getLastError() -- Classic ASP Debugging

Dork — Tue, 31 Jul 2007 20:17:55 GMT

Hello Everyone,

I just got my Vista Ultimate machine. It's awesome, and like most of you I'm having some issues with IIS 7.0 when it comes to my classic ASP websites. I wonder if anyone can successfully utilize the Server.getLastError() object? I typically setup my ASP sites to redirect to a local ASP script where there's a 500 IIS error code, display a user friendly message to the user, and log the error details using Server.getLastError(). While I'm able to get IIS 7.0 to redirect the user to the appropriate script, I cannot seem to access any error details. Here's what my code looks like...

Set o = Server.getLastError()
Response.Write "AspCode: " & o.AspCode & ""
Response.Write "Category: " & o.Category & ""
Response.Write "File: " & o.File & ""
Response.Write "Description: " & o.Description & ""
Response.Write "Source: " & Server.HtmlEncode(o.Source) & ""
Response.Write "Line: " & o.Line & ""
Response.Write "AspDescription: " & o.AspDescription & ""
Set o = Nothing

Instead, the error line is always returning a 0.

Same "Jump to URL" expression within SQL Reporting Services working on 1 server but not another

him19010 — Thu, 11 Jan 2007 18:17:03 GMT

This seems like an IIS issue so I am trying it here as a last resort.

I have the following 2 "Jump to URL" expressions in a report:

=BLOCKED SCRIPTvoid(window.open('http://www.google.com','_blank'))

and

=BLOCKED SCRIPTvoid window.open('http://barn/apx/PortfolioDetail.aspx?linkfield=749', '_blank')

There are quotes around the whole expression for both of them. Both of these expressions work on 1 reportserver but not another (within exact same report). Has anyone else had similar issues?

The reportserver that works is on IIS v5.1 and SQL 2005 on a XP SP2 machine. The reportserver that does not work is on IIS v6.0 and SQL 2000 on a Win2003 SP1 machine. The report is exactly the same (even the dataset sources are the exact same) and it is deployed on 2 different machines as above.

Could the IIS version difference be the issue? TIA.