Julian4145
Programmer
Hey all,
Any ideas on this one would be greatly appreciated. I currently support a small vb app written VB 6.0 that was written before I was hired. The app has about 12 users.
Backgroun Info:
The company is in the process of rolling out XP Pro to all PC's. So some users are on NT, while others including myself are on XP Pro. We are also running Novell utilizing Roaming Profiles so that users can access their own desktop no matter what PC they log into.
The Issue:
All of the approx. 12 users were on NT. When they were on NT, the app ran fine without issue. All the users then got upgraded to XP Pro. Once this occurred, the app started sporadically breaking. The error we would get is a 713 run-time error with a class id which corresponded to msbind.dll. Most often the app breaks after logging off their native PC, logging into a different one, then logging back in to the original. Which suggested to us there is an issue with the Roaming Profile and the dll's the app references and uses. To confirm this we installed the app on a freshly imaged PC, installed RegSafe, so we could snapshot the Registry before a user logged off, which we did. Then we had the user log into a new machine, as soon as they logged in, they logged off of that one, and then logged back into the original machine the app was installed on. After they logged back in, the app would break. When we re-registred the MSBind.dll, the initiall 713 error we were getting was fixed, but as we continued to use the app we started getting similar errors that used other .dlls. We took another snapshot of the registry, and did a compare of the first snapshot. All the .dlls that the app had installed or registered were deleted completely from the registry, including HKEY_USERS and HKEY_CLASSES_ROOT. This is a big issue because the app is a data entry app with some temp users that don't necessarily have their own PC. So they need to be able to move around to other PC's.
Any ideas on what could be causing this, and what we could do to fix it? Let me know if there is any additional info anyone needs. Thanks.
Julian
Any ideas on this one would be greatly appreciated. I currently support a small vb app written VB 6.0 that was written before I was hired. The app has about 12 users.
Backgroun Info:
The company is in the process of rolling out XP Pro to all PC's. So some users are on NT, while others including myself are on XP Pro. We are also running Novell utilizing Roaming Profiles so that users can access their own desktop no matter what PC they log into.
The Issue:
All of the approx. 12 users were on NT. When they were on NT, the app ran fine without issue. All the users then got upgraded to XP Pro. Once this occurred, the app started sporadically breaking. The error we would get is a 713 run-time error with a class id which corresponded to msbind.dll. Most often the app breaks after logging off their native PC, logging into a different one, then logging back in to the original. Which suggested to us there is an issue with the Roaming Profile and the dll's the app references and uses. To confirm this we installed the app on a freshly imaged PC, installed RegSafe, so we could snapshot the Registry before a user logged off, which we did. Then we had the user log into a new machine, as soon as they logged in, they logged off of that one, and then logged back into the original machine the app was installed on. After they logged back in, the app would break. When we re-registred the MSBind.dll, the initiall 713 error we were getting was fixed, but as we continued to use the app we started getting similar errors that used other .dlls. We took another snapshot of the registry, and did a compare of the first snapshot. All the .dlls that the app had installed or registered were deleted completely from the registry, including HKEY_USERS and HKEY_CLASSES_ROOT. This is a big issue because the app is a data entry app with some temp users that don't necessarily have their own PC. So they need to be able to move around to other PC's.
Any ideas on what could be causing this, and what we could do to fix it? Let me know if there is any additional info anyone needs. Thanks.
Julian
