Troubleshooting Code 800A03F2 – Expected Identifier
Introduction to Code 800A03F2
When you get Error code 800A03F2 concentrate on the Line: number and especially the Char: number. Once you trace the line and position, you should be able to identify the problem. A wild guess is there is an extra full stop.
The Symptoms You Get
The script does not execute as you hoped, instead you get a WSH error message.
The Cause of Error 800A03F2
Your VBScript contain is missing a character. Note: the clue ‘Source: Microsoft VBScript compilation error’. My point is that ‘compilation error’ and not a ‘runtime error’, means this is a syntax error in your script.
Another cause is because VBS does not support the Optional statement for Subs and Functions. See example 3.
The Solution to Expected Identifier
This is a syntax error, therefore check for a missing argument. In my example, Windows Scripting Host is telling us that the problem is at Line: 3, count blank lines and lines with remarks. In this case the Char: number (73), is very useful in tracing the error. Something is wrong with the syntax at the end of the line 3.
Example 1 of Code 800A03F2 error
Note: The Line: 6 Char 34 , .T.)
It should be , True)
Example 2 of Code 800A03F2 error
WScript.Echo strDriveLetter & " drive is mapped to " & strUncPath.
Here is the tiniest of errors, an unwanted full stop (period) after strUncPath.
Example 3 Optional Statement Problem
Kindly sent in by Robert Dunham
Here, the 800A03F2 is raised because VBS does not support the Optional statement for Subs and Functions and was expecting a valid variable name. Here’s the code sample:
This error would also be raised for an incorrectly spelled byVal or byRef statement.
While this is very similar to your first example, I wanted to point out that this error can happen during declaration as well. The above example would be very common for those who are used to standard VB programming.
See More Windows Update Error Codes 8004 Series
Windows Management Instrumentation (WMI) is one of the hidden treasures of Microsoft operating systems. Fortunately, SolarWinds have created the WMI Monitor so that you can examine these gems of performance information for free. Take the guess work out of which WMI counters to use for applications like Microsoft Active Directory, SQL or Exchange Server.
Do you need additional help?
Give something back?
Would you like to help others? If you have a good example of this error, then please email me, I will publish it with a credit to you:
If you like this page then please share it with your friends