Asp Error 0241
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us active server pages error 'asp 0115' Learn more about Stack Overflow the company Business Learn more about hiring developers or
A Trappable Error (c0000005) Occurred In An External Object. The Script Cannot Continue Running.
posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow unexpected error a trappable error Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Classic ASP : C0000005 Error on execution up
A Trappable Error C06d007f Occurred In An External Object The Script Cannot Continue Running
vote 5 down vote favorite 1 I'm trying to execute classic ASP pages on a windows 2008 64 bit R2 box. Initially the problem was with registering dlls : That's now fixed. register dll in on windows 2008 r2 Now when I try to access the page I get this error Active Server Pages error 'ASP 0241' CreateObject Exception index.asp The CreateObject of '(null)' caused exception C0000005. Server asp_0115 object error 'ASP 0177 : c0000005' When I change the code from Server.CreateObject to CreateObject .. I end up with this error Active Server Pages error 'ASP 0115' Unexpected error index.asp A trappable error (C0000005) occurred in an external object. The script cannot continue running. I checked everything I could - Access and admin rights etc. The application pool are set to No Managed Code + Classic mode. Any ideas to fix this? windows asp-classic windows-server-2008-r2 share|improve this question asked Jan 10 '11 at 17:17 Broken Link 1,06981943 1 What Object are you Creating? –bzlm Jan 10 '11 at 17:27 What is the object you are trying to create? –Sparky Jan 10 '11 at 17:27 It's a custom object. Retrieves some stuff from db. I have the dll registered. No source code tho. –Broken Link Jan 10 '11 at 17:35 Try writing a small .vbs file that create the object, just to rule out problems in the component itself. Maybe the components depends on some outside file, ODBC registry, etc. –Eduardo Molteni Jan 10 '11 at 19:24 This links may help 15seconds.com/faq/Errors/476.htm and 15seconds.com/faq/Errors/362.htm –Eduardo Molteni Jan 10 '11 at 19:2
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Active Server Pages Error "ASP 0241" Microsoft ProClarity > ProClarity - General Question 0 Sign in to vote HI We just posted the same issue a few hours ago on a previous post, but feared it might not be noticed as the post does http://stackoverflow.com/questions/4649487/classic-asp-c0000005-error-on-execution seem a bit dated - hence posting again. We're using ProClarity Analysis Server v6.3.2217 on Windows Server 2003 R2 and have not upgraded ProClarity or Analysis Services recently i.e. the configuration has remained the same throughout, yet, an unexpected issue cropped up yesterday where the following symptoms were https://social.technet.microsoft.com/Forums/en-US/a74a4904-4fd7-4b9e-bc4a-7489235ec489/active-server-pages-error-asp-0241?forum=proclarity witnessed - 1. On the Libraries web page (on individual users' browsers), we see the error: Active Server Pages error ‘ASP 0241’ CreateObject Exception 2. When attempting to open a book, we see the following error: The website cannot display the page 3. In the event viewer for the ProClarity Analytics Server Administration Tool, there were a number of errors around this time, predominantly: Error: File /pas/en/src/PHomeRight.asp CreateObject Exception. The CreateObject of '(null)' caused exception C0000005 A trappable error (E06D7363) occurred in an external object. The script cannot continue running. While we couldn't find any conclusive posts on the web, a simple restart of the IIS service seemed to solve the issue, temporarily at least. However, the same issue resurfaced this morning and just as yesterday, all business users lost connect
help? Post your question and get tips & solutions from a community of 418,430 https://bytes.com/topic/asp-classic/answers/57525-asp-iis-errors-custom-com-call IT Pros & Developers. It's quick & easy. ASP/IIS errors on Custom COM call P: n/a Steve All -- This occasionally happens, and there's no set pattern on http://support.softartisans.com/Forums/ShowPost.aspx?Postid=4240 why this is... perhaps it happens a few times every few months or so. I have a custom ATL COM object that handles data from multiple pages a trappable and sites on my server. Occasionally, I'll get the following errors: ASP_0241|CreateObject_Exception|-|ASP_0241|CreateObject_Exception|42|ASP_0177_:_c00 00005|Server.CreateObject_Failed 500 Which sometimes is followed by (in no particular order) 800a01fb|An_exception_occurred:_'function name' function name isn't always the same, but is always one in my COM object. The problem associated with this error is that the object cannot be created again until IIS is a trappable error restarted. This object controls a very vital part of the site, and all users will typically get the: Active Server Pages error 'ASP 0241' CreateObject Exception /Site/account.asp The CreateObject of '(null)' caused exception C0000005. Server object error 'ASP 0177 : c0000005' Server.CreateObject Failed /Site/account.asp, line 42 c0000005 This custom COM object has been successfully deployed for nearly two years, and under intense traffic at times. One of the things I'm thinking is that I return an S_OK when I trap an error... so try{ blah } catch (mycustomerrorclass& err) {} catch (...) { tell something an odd error occured } return S_OK; It seems like once the (...) is caught, the other errors appear... or vice versa. Do you think I should be returning E_FAIL in that catch all statement? This COM object uses no external COM objects (ado, etc). The only idea I can think of if to try the E_FAIL, but I thought I successfully have caught the error. Is this not the case