Unable to update mood on Windows x64 laptop
Submitted by Anonymous on Fri, 12/17/2010 - 03:24.
I was able to make SyncMood work with Windows XP 32-bit. I have a laptop with Windows 7 Home Premium 64-bit, and whenever I try to update the mood (with Skype running) I get the following error:
Initialize connection to Skype. Please allow this application to access Skype.
ERROR: Error during Skype Mood update: Retrieving the COM class factory for component with CLSID {830690FC-BF2F-47A6-AC2D-330BCB402664} failed due to the following error: 800700c1.
Thoughts/suggestions?
Thanks,
George
ERROR: Error during Skype Mood update: XML node is empty.
Oddly, other than this error, there seems to be no interaction with Skype. At no point does Skypemood appear to ask for permission to interact with Skype.
Unable to update mood on Windows x64 laptop
Hi,
Thank you for your feedback, we fixed the problem. We have just released a new version of SyncMood labeled as 1.4 wit support of Skype on 64 bit platform.
Download an new version from http://synqit.com/SyncMood/Download
Unable to update mood on Windows x64 laptop after SP1
This is the OP, and I unfortunately didn't get to test the fix on 1.4 before I made the Windows 7 x64 SP1 update this past Tuesday.
I tried SyncMood 1.4 on my laptop, and it had a Connection refused error. What's weird is that usually I get a popup dialog in Skype asking me to allow access, and I never get that popop. Nevertheless, I went into Skype settings and saw SyncMood.exe listed as not allowed. So next, I made sure to that SyncMood.exe was updated to "Allow this program to use Skype." I then restarted Skype and SyncMood, just in case. None of my attempts worked, and I'm beginning to suspect that either SP1 is the culprit (even tho I never tested on a non-SP1 W7 x64 laptop) or the latest version of Skype.
My version of Skype is 5.0.0.156.
Here is the error log from my last attempt:
2011-02-26 14:06:21,510 INFO SyncMood.Program - Tweet2Skype started.
2011-02-26 14:06:21,526 INFO SyncMood.GuiHelper - OS version: [Microsoft Windows NT 6.1.7601 Service Pack 1]
2011-02-26 14:06:21,528 INFO SyncMood.GuiHelper - Processor architecture: [x86]
2011-02-26 14:06:21,528 INFO SyncMood.GuiHelper - Application version: [1.4.0.0]
2011-02-26 14:06:21,805 INFO PublicLog.MainFormController - Timer set to 5 minutes
2011-02-26 14:06:21,905 INFO PublicLog.MoodUpdater - 2:06:21 PM - Starting Skype Mood update
2011-02-26 14:06:22,200 INFO PublicLog.MoodUpdater - Received tweet: [REMOVED TWEET]
2011-02-26 14:06:22,203 INFO PublicLog.MoodUpdater - Initialize connection to Skype. Please allow this application to access Skype.
2011-02-26 14:06:22,355 ERROR PublicLog.MoodUpdater - Error during Skype Mood update: Connection refused.
2011-02-26 14:06:22,357 ERROR SyncMood.MoodUpdater - Exception in MoodUpdater.
System.Runtime.InteropServices.COMException (0x80040204): Connection refused.
at SKYPE4COMLib.SkypeClass.Attach(Int32 Protocol, Boolean Wait)
at SyncMood.SkypeHelper.InitSkypeConnection()
at SyncMood.MoodUpdater.DoTheJob(SyncSettingsTwitter syncSettings)
I was about to fire up .NET reflector, but I'm afraid I don't have it at the moment, so I am a little stuck at this point.
Thank you for making this free.
-George
Unable to update mood on Windows x64 laptop after SP1
Hi George,
The "Connection refused" error means that your Skype instance refuses connection request from the SynqMood or request was timeouted.
May be connection request is timeouted because you didn't allow the connection?
Check for the "Allow Connection" dialog inside Skype window, for Skype version ver.5.x it is not a popup but dialog on the top-right side of your Skype window, similar to
Hope, this helps.
Regards, Andrej
I get the same error
Oddly, the error occurs even though the mood updates successfully. Yet every 5 minutes I get a balloon saying it failed. At no time do I get an allow access / deny access dialog.
Huh, for some reason, when I
Huh, for some reason, when I switched my view in Skype from Compact View to Default View, I finally saw that dialog.
All in all, it works now. Thanks guys!
-George