Runtime Error 9 [subscript out of range at logon]

Hi guys, i have a machine that belongs to a network and each time the user tries to long in he gets an error message "runtime error 9 - subscript out of range "

The message does not prevent the user from working, he just needs to click ok so its more annoying than a problem. However id like to remove it. Its at an early stage of investigation but one thought of mine is that its a user profile issue. Therefore i will attempt to log into the machine and replicate the error message as soon as possible.

I just thought id post it in case any of you guys have seen this before and you could save me some time.

Thanks in advance.

 

It would be useful to know if the message only occurs when the user logs on to a particular PC, and if other users logging on to that PC get the same error message.

However, if I was to guess with the information so far, I'd be looking at logon scripts within the users Group Policy.

 

The message only appears on this one machine and also appears when others try to log in to it. Therefore its not user specific.

Might look into the login scripts.

 

OK

As a programmer I can tell you what a subscript error is.

Some program have a range of acceptable numbers. Can be 1-10 or -1000 thru +10000 whatever. So something has fed this program a number outside this range. Or it has fed it an Alpha character such as abcd instead of a number.

Very unlikely to happen in a clean OS environment but can happen as things are added, device drivers, resident programs even M$ updates.

SO! In order to trouble shoot tis issue do the below. And let me know.

1. Boot safe mode minimal.
If problem does not exist do step 2 below.

2. Boot safe mode with networking.
If problem exists it is network related.
If it does not then it is likely a startup program that is causing the issue.
For either or both of these issues go to step 3.

3. Download Mike Lin's StartupCtl http://www.mlin.net/files/StartupCPL_EXE.zip

Use it and uncheck all startups and reboot.

If problem still exists then time to drop back and punt.

If problem does not exist then put the checks back one at a time till you find the problem startup.

You have the ball!

Bob

 

hellooooo!

 

Patience Bob. Reactions can take a little while.

 

Sorry mate..just now saw ur post...i have being very busy the past two days with other stuff...i will try this now straight away and post back

Sounds like good advice anyway

 

Took pc out of network and ran boot up in safe mood.

This worked

Good advice members