Run dll error message when users logon - vmsvpl.dll

When the domain users with redirected user accounts logon they get this error message 4 times.  

There was a problem starting \\server\share\user directory\application data\vmsvpl.dll

The specific module could not be found.
LVL 1
ehessAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

piattndCommented:
What do you mean by "redirected user accounts"?
0
ehessAuthor Commented:
The user's profiles have redirected folders instead of local user profiles.
0
Life1430Commented:
is there any startup script or programme defined with this path please post "gpresult /h c:\gp.html" from client end
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

piattndCommented:
This still isn't making sense....

When a user logs in with a roaming profile, the contents of the roaming profile are cached to a local profile.  You may be removing that local profile after the user logs off, but that information is still cached down.

Along with that, you usually redirect the users my documents and desktop to a network share so you don't bloat the size of the profile.

This link describes that process:
http://technet.microsoft.com/en-us/library/hh848267.aspx

Having said that, can you confirm that when the user logs in, a local profile gets created?
0
piattndCommented:
Also, is this impacting every single user or is it just this one machine?
0
ehessAuthor Commented:
Yes, a local profile is created, but the type of profile is a roaming profile.  

The accounts are a hybrid of roaming profiles and redirected folders.  I setup the roaming profiles on server 2003, then when 2008 came out I moved the My Docs, Desktop and App Data to redirected folders (network share).  

Truthfully, I just never cleaned up the profile structure, rather made the changes that I needed to for Server 2008 and 7. All the users that use the computers in the room (2 computers, with 10 users) get the dll errors.  

Any user that logs into the two computers gets the errors, but don't get the errors on other computers on the domain.  Users who don't have roaming profiles don't get the error.  I'll check the app data folder permissions tomorrow.
0
piattndCommented:
Are the other computers the same operating system?
0
ehessAuthor Commented:
Yes, both Windows 7.
0
piattndCommented:
I mean the working computers.  Are they all windows 7 as well or are they windows XP (or other OS).
0
ehessAuthor Commented:
The working computers are all windows 7.
0
piattndCommented:
Are there any userenv errors logged in the windows system event log that correlate to the time of the dll error messages?  If they aren't the source of userenv, are there any errors at all in either application or system log that indicate an error regarding the dll (perhaps the calling software)?

Originally I was thinking permissions or profile corruption, but if it works just fine from other computers, I don't see why it would be an issue on these 2 and not those.  Are there any significant differences between these windows 7 machines and the working ones?  Did you find any programs that auto start when the user logs in?  (I think a previous expert posted about this, though I didn't see an answer)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ehessAuthor Commented:
I found the problem.  I didn't bother to check for userenv errors or even the event logs.  I checked the startup folder for the users and found nothing.  I then ran msconfig (system configuration) and checked the startup tab.  

Sure enough I found the culprits.  I disabled all four of the startup items with the names int the corresponding dll error messages.  I restarted and logged in.  No dll error messages on the login.  Yay!
0
piattndCommented:
Cool, glad you got it all fixed!  Sorry it took so long to get to that point!
0
ehessAuthor Commented:
There was no startup script and nothing in gpresults.
0
piattndCommented:
Are you making a statement or are you inquiring how the items got into startup in msconfig?  :)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.