Microsoft Online Services Sign in reports: Application is unable to connect
-
Wednesday, June 17, 2009 2:26 PMWe are a new BPOS customer. Using the Sign In tool for all users. For a couple users the login works fine. After logging in the first time the tool wants to config Outlook, Live Meeting and Communicator. Instead of configuring them under each app in yellow the Sign in tool reports:
Application is unable to connect; if this problem persists, contact your service administrator.
At the bottom of the app one can see her name and "Sign out"
Answers
-
Tuesday, June 23, 2009 4:28 AM Solution found:
The cert store for the user did not have the permissions set correctly. Ran the following command:
cacls "%appdata%\Microsoft\Crypto\RSA" /t /e /c /g %userdomain%\%username%:F
- Marked As Answer by Nathan Sm Tuesday, June 23, 2009 3:04 PM
All Replies
-
Friday, June 19, 2009 8:27 PMModeratorAre you able to sign-in to the Sign in tool successfully?
Did you ensured to close all the IE instanes (you can do so by go to Task Manager - Processes tab - kill all "iexplore.exe"
Please make sure you close Outlook (you can do so by go to Task Manager - Processes tab - kill outlook.exe
After ensuring all these applications are closed, please exit the client (right click on sign-in tool icon in the system tray icon and click on exit) and Sign-in again and verify configuration works fine or not.
You can also try to reconfigure the applications by Sign-in to Signin tool - go to options tab - Expand "Advanced Options" - Click on "Reconfigure my desktop applications" link
If none of the above helps, please provide the sign-in tool log files.
The log file can be found in vista - %localappdata%\Microsoft\Sign In\logs
in XP - C:\Documents and Settings\<user name>\Local Settings\Application Data -
Tuesday, June 23, 2009 4:28 AM Solution found:
The cert store for the user did not have the permissions set correctly. Ran the following command:
cacls "%appdata%\Microsoft\Crypto\RSA" /t /e /c /g %userdomain%\%username%:F
- Marked As Answer by Nathan Sm Tuesday, June 23, 2009 3:04 PM
-
Monday, June 29, 2009 2:11 PMThis error comes back!
Even after we have connected the applications and used them for a day - this error comes back. Anybody else see this behavior? -
Monday, August 24, 2009 9:59 PMwe have the same issue. have had this issue since we began this service.
login once...works. log out..cannot get back in. I cannot believe this issue has not been resolved. We have other users on this and is working without issue. Only 2 of the end users have the issue. Anyone help on this?? -
Friday, January 22, 2010 5:04 PM We have the same problem, running the command above fixes the problem for one log-in only.
We are running the 30 day trial and had intended to move the company to BPOS, but I doubt we will make the change based on this problem.
It is amazing that this is the only search result for "Microsoft online" + "application is unable to connect"
Does anyone have any ideas????- Proposed As Answer by DevonBlues Tuesday, January 26, 2010 12:00 PM
-
Tuesday, January 26, 2010 1:31 PM
Check that the time on the workstation is correct. Please see recent solution posted by BPOS support for a similar connection problem we experienced.
Issue Resolution:
Arturo Gonzales had you make sure that the clocks on your users' computers are set to the correct time and to the correct time zone.
(According to the knowledge base articled at http://support.microsoft.com/kb/961487 this error could indicate that your system clock is off by more than 5 minutes or is set to the wrong time zone and you should reset your system clock and attempt log into the Sign In Application again. You can automatically synchronize your clock by opening a command prompt through hte Start Menu - Run - Type "CMD" - Press Enter - Type "net time/set /y" - Press Enter - Close the command prompt Window.)
My advice for what its worth is BPOS will solve many of the problems experienced running Exchange Server namely upgrade/migration capital cost/overheads, GP & storage issues, sharepoint sync, mobile integration & remote access however it will come with its own issues namely password maintenance, quirky management consol, Poor Office 2003 compatability and the general cloud problem regarding uptime but all in all I won't be going back to a local exchange install. -
Monday, November 08, 2010 12:28 AM
Hi,
I had another case like this, and have a few additional troubleshooting steps:
Connect to https://autodiscover-red001.mail.microsoftonline.com/autodiscover/autodiscover.xml and if you get "server is too busy" you are going to have to give us a call at 1-866-676-6546 Option 1, or create a Service Request (SR) in the Administration Center.
If it resolves to xml text you may simply have a connection issue, or your subscription changed from a standard to a deskless worker license (although that would typically result in Outlook, and Live Meeting not being shown as options in the Sign in Application).
In the case I just resolved the customer was missing a registry entry for a domain that caused autodiscover to not resolve in the Sign in Application. Root cause still TBD, but resolved by performing a full uninstall of the Sign in Application, and then re-install, or copying the registry entry from another user who connects successfully, and adding it to the troubled machine should work as well.
Note: Create a system restore point whenever making changes to the registry. Also you can verify domains in the registry under HKCU>Software>Microsoft>Office>12.0>Outlook>AutoDiscover.
Neither of these options is "nice", but the Sign in Application should configure everything on its own, and even update the registry when a new domain is added to the account. Hopefully this helps if not call 24x7, and we'll do our best :D
Actually now that I think about it you could change the default login to the .microsoftonline.com alias login with that, and then reconfigure desktop applications. That should force the update withouthaving to manually edit the registry. (in theory)
.png){kind=spacer}
