Microsoft Vbscript Runtime Error 800a000b
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/General ASP.NET/Getting Started/Obscure division by zero error, comes and goes. Obscure division by zero error, comes and goes. [Answered]RSS 10 replies Last post Apr 27, 2012 09:35 AM by deepak.vasudevan ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Reply mrman912 None 0 Points 4 Posts Obscure division by zero error, comes and goes. Apr 25, 2012 03:23 PM|mrman912|LINK Good afternoon all, I've been wrestling with this problem for a few days now on an intranet page and am at the end of my rope, so I thought I'd throw it out here to see if anybody has a good idea. The section of my code where the error is thrown looks like this: if not isNull(rc("TotalMeters")) and rc("TotalMeters") <> 0 and not isNull(rc.Fields(i)) then tm = rc("TotalMeters") Response.Write("TM: '" & tm & "'") if (rc.Fields(i) * 100) / tm > 5 then rclass = "Alert" end if I'd insert a screenshot of the page, but that's not allowed. The erroring region looks like this: TM: '120' Microsoft VBScript runtime error '800a000b' Division by zero /communications/towerstats2.aspx, line 173 I can't for the life of me determine how dividing a number by 120 can trigger a division by zero error. Help? Thanks very much for your time, -Mike Reply ignatandrei All-Star 119052 Points 27465 Posts ModeratorMVP Re: Obscure division by zero error, comes and goes. Apr 25, 2012 11:58 PM|ignatandrei|LINK before dividing, verify if tm is not zero. .NET Teacher | .NET Videos 5 minutes Reply cnranasinghe Contributor 6551 Points 2248 Posts Re: Obscure division by zero error, comes and goes. Apr 26, 2012 12:05 AM|cnranasingh
internal server error + Ask a Question Need help? Post your question and get tips & solutions from a community of 418,590 IT Pros & Developers. It's quick & easy. Microsoft VBScript runtime error '800a000b' vs HTTP 500 - Internal server error P: n/a I am accessing the same error-containing ASP page on an ISP server using w2k IE6 but with different effect. On the first computer I get several line of HTML outputed by ASP, shown correctly by the browser, followed by a descriptive error message: Microsoft VBScript runtime error '800a000b' Division by zero followed by the number of the error-making line On the second machine my HTML is not displayed at http://forums.asp.net/t/1796961.aspx?Obscure+division+by+zero+error+comes+and+goes+ all. Instead I am getting that meaningless error page sayng that The page cannot be displayed, HTTP 500 - Internal server error. How can I get the second computer be more informative about the errors? Jul 19 '05 #1 Post Reply Share this Question 10 Replies P: n/a Curt_C [MVP] it's an IE setting. Uncheck the "Show Friendly Error Messages" option -- Curt Christianson Owner/Lead Developer, DF-Software www.Darkfalz.com
The runtime error 800A000D is straightforward to solve. The secret is to read the Windows Script Error message carefully, then locate the line number with the Type Mismatch. Introduction To Error Code 800A000D This runtime error, 800A000D occurs when you execute a VBScript. My http://www.computerperformance.co.uk/Logon/code/code_800A000D.htm suggestion is that there is a VBScript statement that does not understand a keyword you are using in your script. Alternatively, you may not be running the script as an ordinary user and not as an Administrator. The Symptoms You Get 800A000D The script does not execute as you hoped, instead you get a Microsoft VBScript runtime error. One possibility is that you are using a WSH object or method that has been misspelt.Chuck kindly wrote in saying that another cause microsoft vbscript maybe that you are logged on as ordinary user, and not an Administrator. The Cause of Code 800A000D Your VBScript contains an illegal method, probably due to a typing mistake, an extra letter. Look for a clue opposite the phrase Error: Type mismatch.... In particular, double check the spelling of your objects.Note 1: Source: Microsoft VBScript runtime error. This is not a syntax error in the sense of a missing bracket, more a typo in the keyword mentioned in the Error: microsoft vbscript runtime line of your WSH Message.Note 2: Error: Type mismatch: 'Join'. Chuck says this could mean that you are logged on as an ordinary user and not an administrator. Note 3: What I have found, is that there need not be any errors per se in the script in order to receive the type mismatch join error. But what the cause has been for two of my recent experiences, is that the user in question, is only a part of a single group that isn't 1. A domain built-in group. 2. Query based distribution groups. The join statement fails in this case because the CurrentUser.MemberOf only contains a single value so when it tries to append the next value, there is no array for it to search through. One fix would be to add error handling around this statement, so that if it fails, it runs the same line except without the join statement. The other option is of course to ensure your users are a part of more than one security or static distribution group. I haven't experimented with whether local domain, global or universal have an effect on this either, but I would imagine not. Nathan Bicknell The Solution of Runtime Error 800A000D Check the spelling of your variables and methods. Look for clues particularly the Line: number and check the Char: references. In the example it is Line:14 Char: 1. In this instance the: 'Error: Type mismatch: 'CreateeObject'' tells u