Home › Forums › Archives › Instant Messaging › Windows Live Messenger Support › WLM only works on one XP user account
- This topic has 14 replies, 3 voices, and was last updated 18 years, 5 months ago by
Doris Kenney.
-
AuthorPosts
-
August 30, 2007 at 2:38 am #27530
DrBroccoli
ParticipantSo I installed WLM… and found out it only works from my user account.
By work, I mean, let’s me log in, and by not work = it opens, but typing and mouse movement over it is VERY laggy and upon hitting “connect” it shoots off an error right away, doesn’t even try.
I’ve tried to install it from other user accounts, and I’ve tried using the public release and the public beta.
All users are computer admins, so it’s not a security restriction.
Any help would be amazing.
August 30, 2007 at 12:02 pm #163630Doris Kenney
ParticipantI’m happy to try and help you. I’ve spent quite a bit of time researching WLM connection problems. And I apologize, but I need a bit more info:
1. Did the machine you installed this on ever have WLM on it where it functioned properly? If so, when did it start not operating properly (i.e. recent upgrade or change to computer)?
2. Have you configured your firewall to allow WLM (and which firewall are you using)? Are you using a router?
3. Which version of WLM is currently on the machine? What operating system are you on?
Sorry for all the questions, but connection issues can be a result of many different causes. I just want to head in the right direction.
-Doris-
August 31, 2007 at 2:09 am #163626Philip
ModeratorAlso, can you sign in to Web Messenger? As Doris has stated, it helps us if you could give us as much information and details as possible about your problem.
August 31, 2007 at 12:15 pm #163621DrBroccoli
Participant@patndoris 222456 wrote:
I’m happy to try and help you. I’ve spent quite a bit of time researching WLM connection problems. And I apologize, but I need a bit more info:
1. Did the machine you installed this on ever have WLM on it where it functioned properly? If so, when did it start not operating properly (i.e. recent upgrade or change to computer)?
2. Have you configured your firewall to allow WLM (and which firewall are you using)? Are you using a router?
3. Which version of WLM is currently on the machine? What operating system are you on?
Sorry for all the questions, but connection issues can be a result of many different causes. I just want to head in the right direction.
-Doris-
1. It used to have WLM, but I’ve always been the user of it, so I never could test that problem. We just got a Foreign Exchange Student and he uses WLM and it will not work on his name.
2. I am using a Firewall, I can connect fine from one name, just not the other.
3. Windows XP with WLM 8.5.123.0601
Tonight I can get you the exact error code when I try to connect, right now, I have to go to class.
August 31, 2007 at 1:36 pm #163629Doris Kenney
ParticipantYou’re on a BETA version of WLM. Betas are notoriously buggy & problems are bound to come with them (that’s why they’re betas.) I found quite a few posts on other forums about sign in issues with 8.5 (although none exactly what you describe.) You didn’t say, but I assume you’re on XP SP2, as the beta version will not function properly on SP1.
My advice before you start looking at other possible causes would be to COMPLETELY uninstall the beta version (see this thread for how to do it https://bigblueball.com/forums/wi…tml#post206523 ) Then install the latest current stable build of WLM 8.1.0178.00 & see if that corrects the problem.
If not – you’re no worse off than you were & you’ve eliminated a beta bug as the root of the problem. I still have a few other ideas floating around in my head, but knowing you’re on beta makes that the #1 suspect, plus it’s hit or miss if typical solutions will even work on a beta version.
Let me know if this fixes the problem. In the mean time – can your exchange student connect using the web based version?
-Doris-September 2, 2007 at 5:54 am #163622DrBroccoli
ParticipantThanks, but as I stated in my first post, I’ve tried the beta and the public release, neither makes a difference.
September 2, 2007 at 5:13 pm #163631Doris Kenney
ParticipantI know this is painstaking but I’m sure it can be resolved. Every detail, no matter how unimportant it seems, can help us help you figure this out. I’m going to attempt to put these questions/suggestions in a logical order so you don’t have to switch back & forth between accounts. Please do this after a fresh reboot of the computer.
** Can you please login under your user account, open WLM & go to Tools/Options/General on the WLM Menu. Please make sure the checkbox Automatically start WLM when I start Windows is NOT ticked.
** Then please go to Tools/Options/Connection & be sure no warnings are showing on the top area of the screen. Click the Advanced Settings button at the bottom of the screen. On the next screen make sure all the fields are blank & hit the Test button in the TCP section. It should pop up telling you “Success you can now connect to the WLM service” then you can close that pop up screen & click OK & OK again to exit the tools menu.
** Sign out your login to WLM & try to connect to his login under YOUR user account. What happens? If an error comes up EXACTLY what does it say? Click the troubleshoot button if it shows & tell me exactly what it says tool.
** Completely close WLM under your user account Just signing off & closing it does not shut it down completely. Please right click the icon in the system tray & choose Exit. Then switch over to his user account on XP.
** When you open the WLM login screen under his account is the “remember me” checkbox ticked to save his login? If so, please click “forget me” so it’s all fresh going through the next steps.
** Please try to login in to YOUR WLM login under his user account. Can you do so? If not, what error comes up & what does the troubleshoot button give you? If you can connect, then please signout of your login & continue.
** Using his WLM login, when he clicks Sign On, EXACTLY what happens & what does the error you get say specifically? Again, click on troubleshoot & tell me exactly what it says.
I’m sorry for all the additional questions, I know how frustrated you must already be. I really want to try my best to help you get up & running on both user accounts. I’m sure some of this will seem frustratingly repetitive to you, but it will help me try & identify the problem a little better. The details are very important. If it does connect at any point under either login or account, please also note where (if at all) the performance of the program seems to be slow – it was a bit hard to tell based on your first post.
-Doris-
September 3, 2007 at 5:03 pm #163623DrBroccoli
ParticipantI can login under anyone on my XP account.
Even with WLM completely closed, and on his XP account, I still get the same error: 800401f3
I Googled and found a few methods, none of which worked, but they can be found here: here. I’ve done everything, except when I try to register mxml3.dll, it gives me another error: 0x80004005. I’ve Googled that to death and have replaced that DLL many times.
I’m not sure if I said this, but the place to time in the username/email is VERY sluggish. Then, when I hit “Log In”, it doesn’t even attempt to, that error pops up right away.
To clarify:
I can only login on my XP account, anyone WLM username will login.
Nothing will login from his XP account.
WLM is only sluggish on his XP account, mine is fine.
September 3, 2007 at 6:14 pm #163632Doris Kenney
Participanthttps://bigblueball.com/forums/msn-windows-live-messenger-support/38474-msn-windows-live-messenger-faq.html You can try this. It’s the most recent info on this sign in problem I can find.
I believe the slowness on the login screen is related to this error code. Are you running any 3rd party add-on’s to WLM? You’ve not mentioned it but it would be helpful to know if you are as this code can also be a result of such programs.
I did find this rather lengthy post. I will tell you up front registry stuff isn’t my strong point – I’m hoping Philip will take a look at this, see what he thinks & give you his recommendation with regard to this newest .dll problem. But certainly you can read over it prior to trying anything at this point. Windows Update and msxml3.dll Problems. Please help – Windows Update Should you decide to try this before he’s had a chance to weigh in on it, PLEASE make a backup of your registry before doing anything – since improper registry edits can render your system useless.
Please let me know if the first suggestion helps fix the problem or if it still persists, I’m not ready to throw in the towel yet! And thank you for posting the error codes, it makes it much easier to help when we have the details.
-Doris-
September 4, 2007 at 2:24 am #163627Philip
ModeratorHave you tried reinstalling msxml3? Log in to his account, and go to this Microsoft website. Scroll to the bottom of the page, and download the msxml3.msi file. Follow the steps to complete the installation, reboot, and then sign in to WLM on his account.
I wouldn’t mess with the Registry unless you really know what you’re doing. There is a possibility of making things worse. So just try the above and post back. Doris and myself will try our best to help you out, so hang in there!
September 7, 2007 at 9:39 pm #163624DrBroccoli
ParticipantI forgot to mention that, I did install that MSI from MS. It doesn’t work yet.
September 8, 2007 at 2:31 am #163633Doris Kenney
ParticipantI will be blunt – we need SPECIFIC ANSWERS to these questions in order to help you. Partial answers aren’t enough for us to help you solve this. There are lots of causes for IM program problems, some easier to fix than others, but ruling out certain possibilities allows us to focus on those which are left, & then how to rule them out until we get to the root cause. That said…let’s get down to the business of trying to get your WLM working well on all user accounts. Can you please provide the answers to the following:
When you say about the MSI “It doesn’t work yet.” Does that mean:
A) You still get error code 0x80004005 when you try to register the .dll OR
B) You are able to register it but it did not solve the problem?When you say you installed the MSI….Did you specifically do it under HIS user account as Phillip instructed?
Are either of you running a 3rd party add-on to WLM such as WLM Plus, MessPatch, Messenger Discovery Live or any other such add-on?
If you launch WINDOWS MESSENGER under his account are you able to login under his screen name? If so, is it functional (or as functional as Windows Messenger can be LOL)?
Can you login to WebMessenger under his account successfully?
Have you run at least 2 COMPLETE & SEPARATE spyware programs to fully scan your computer. I recommend Ad-Aware as #1 & Advanced Windows Care as the 2nd one as it will also suggest tweaks to improve system performance. But Spybot as a 2nd one would also be a good choice. It goes without saying your definitions should be up to date when you do this.
Have you run a complete Virus scan on the computer? Again…with up to date definitions.
Have you cleaned out your Temp Files (using disk cleanup or Advance WindowsCare is quickest).
Do you know how & have you cleared your prefetch folder? (Just a yes or no to this one….don’t go doing it just yet please.)
This one is certainly posing a challenge for Phillip & I. But I’m still confident we can help you. But we need to know the answers to these questions, & to know you’ve done exactly what is suggested so we can rule out some specific possibilities. Rather than bore you with the reason behind each question…please realize each one really does have a useful purpose in troubleshooting this problem. Stick with us here – we’re gonna do our very best to help you work through this one – but obviously it’s going to require a bit more patience while we sort it out.
-Doris-
September 9, 2007 at 10:09 pm #163625DrBroccoli
ParticipantEven after installing the MSI, I can’t register it. I installed on my name and under his name
No 3rd party programs.
Your third question makes no sense, if I could log on to WLM under his name, I wouldn’t be asking here?
Yes, he can logon to his account on WebMessenger and on WLM under my XP account.
I am not a computer idiot, I have virus scan software and spyware software, trust me, my computer is clean. =D.
No, I haven’t cleared the temp files. The thing is, I made his account, installed WLM and it didn’t work, it’s a brand new WLM account.
No idea about the prefetch folder.
September 10, 2007 at 12:22 am #163634Doris Kenney
ParticipantGetting the .dll to register successfully is the first theng to figure out. With any luck it will fix all the problems. I spent more time Googling & found this thread in another forum Problem register dll… – Wilders Security Forums which mentions a free program called Dependency Walker. I also did a search for it directly & here’s the Wiki on it Dependency walker – Wikipedia, the free encyclopedia I’m generally leary of programs I don’t know much about, hopefully this will be enough for you to determine if it can be of assistance. Seems reputable on the surface.
In my 3rd question I was not referring to WLM but to Windows Messenger which are separate. Often the latter will work even when WLM won’t. However, knowing you CAN log in on WebMessenger & under your XP account with his login negates it anyway.
I certainly did not mean to imply you were a “computer idiot” & apologize if I came across as doing so. Spyware can make programs do odd things & not everyone makes the connection. If you say your computer is clean I believe you, but if I’d not asked I would have been remiss. I certainly didn’t mean to offend.
I do want to see you get this resolved as quickly as possible. I hope perhaps the program listed above may be of some help with the .dll. I’m not gonna ask more questions…at least until we get that .dll to register successfully for you lol. 🙂
-Doris-
September 10, 2007 at 1:24 am #163628Philip
ModeratorOK, try this. Log into the other user’s account. Download the msxml3.dll file from here. Put it into the C:WindowsSystem32 folder. If it says the file already exists, overwrite it. Open a Command prompt, navigate to C:WindowsSystem32, and re-register msxml3.dll. If this succeeds, log into WLM and see whether the problem disappears or not.
-
AuthorPosts
- You must be logged in to reply to this topic.