Activprimary 3 runtime error 9

[bladedanny]

Right, hopefully some one can help me with this as I've tried everything I can think of.

 

Each time the y1 user tries to open Activprimary 3 they get

 

Run-time error '9' - Subscript out of range

 

All other user account it works fine with, so I decided it can't be the application and it must be with the Y1 user account. So I deleted all settings files I could find relating to Activprimary within the Y1 home folder and profile and still get the same error.

 

I have tried the promethean KB and found something similar that related to Activprimary 2 but tried it anyway still no luck.

 

The only thing left I can think to do is copy all the work out of the Y1 home folder and re-create the user and copy all the work back, obviously I don't really want to do this.

 

This happens on all machines in the school, all are running windows XP with latest version of Activprimary 3 in a Server 2003 domain.

Has anyone got any suggestions.

 

Thanks,

 

Dan

[marvin]

Did you cop the ActivPrimary 3 settings folder which is usual created under the local hard drive onto their network work folder?

 

Hope that makes sense!

[bladedanny]

Did you cop the ActivPrimary 3 settings folder which is usual created under the local hard drive onto their network work folder?

 

Hope that makes sense!

 

Yes the folder is created into there network home folder which is also what my documents is mapped to.

[elsiegee40]

It might be a profile issue.

 

I would try adding the user to the administrators security group and move the user to 'Users' in AD (away from GPO restrictions)

 

If the profile is mandatory - rename ntuser.man to ntuser.dat in the profile.

 

Then logon and try using ActivPrimary. Do you still get the problem?

 

Logoff, remove the logon from administrators, put the user back in the correct AD OU and if you've changed ntuser, change that back.

 

Then logon again and see what happens now.

 

Good luck.

[bladedanny]

It might be a profile issue.

 

I would try adding the user to the administrators security group and move the user to 'Users' in AD (away from GPO restrictions)

 

If the profile is mandatory - rename ntuser.man to ntuser.dat in the profile.

 

Then logon and try using ActivPrimary. Do you still get the problem?

 

Logoff, remove the logon from administrators, put the user back in the correct AD OU and if you've changed ntuser, change that back.

 

Then logon again and see what happens now.

 

Good luck.

 

Just been and tried that, still get same error when user is in administrators group and away from GPOs and when moved back. I don't think it will be the GPO or permissions as other users with same permissions and GPO work fine.

 

Thanks,

 

Dan.

[bladedanny]

More info.

 

I have just created a new user for testing, set its home folder to the same as y1 and got the same error, set the home folder to a new one and Activprimary worked fine. It has to be something inside the Y1 home folder, but having deleted the activprimary 3 folder I have no idea as to what.

 

Thanks,

 

Dan

[bladedanny]

Sorted.

 

I decided the only way was the long way, so I copied everything out of the users home folder, tried Activprimary, this worked. So I started to copy things back in a few files/folders at a time and tried Activprimary each time.

 

It turned out that there was a file (no extension) with the name '1' in the top level of the home folder that was the problem. I have now deleted this file and all is working fine.

 

Thanks all for your help and advice,

 

Dan

[elsiegee40]

Sorted.

 

I decided the only way was the long way, so I copied everything out of the users home folder, tried Activprimary, this worked. So I started to copy things back in a few files/folders at a time and tried Activprimary each time.

 

It turned out that there was a file (no extension) with the name '1' in the top level of the home folder that was the problem. I have now deleted this file and all is working fine.

 

Thanks all for your help and advice,

 

Dan

 

 

Glad it's fixed... what an improbable cause!