Answered by:
Outlook Live Meeting Plug-in - Cannot log in

Question
-
We have OCS 2007 R2 deployed in a load-balanced Consolidated Front-end and Consolidated Edge server topology. Using Communicator, I can "Meet Now" both internally and externally without a problem. However, using the Outlook Live Meeting plug-in (latest version), I cannot even log in to meet or schedule a meeting. I receive an error that I've seen on other threads, but haven't found a resolution to.
The error is: "Cannot connect to the server because the information in the User Accounts dialog might be incorrect or improperly formatted. Please verify that this information is correct, an then click Test Connection. If you still can't connect the server might not be available."
The Communicator log under %temp%\Tracing doesn't provide any silver bullets, so I'm unsure how to proceed with troubleshooting. What other tools/logs can I examine to determine the source of the problem?
Thanks!Thursday, July 9, 2009 3:39 PM
Answers
-
OK so when you are on that page where your USER SIP URI is. Click on advanced. once in advanced then add your user name and password in place and check the box to use it. If that does not fix it. Specify the server names in the correct fields for internal put the fqdn:5061
for the external one put fqdn:443 the external fqdn should be your Access edge server which is usually sip.domain.com, the internal fqdn should be your pool fqdn then:5061
Let me know if that works. I am just asking you to test this. so we can determine next steps. I have a list of other things that cause this but I start with easiest first.
thanks.
Mitchr |MCITP:Enterprise Server Admin, Messaging |MCTS:OCS with Voice Achievement |MCT- Proposed as answer by Mitch Roberson Thursday, July 16, 2009 8:48 PM
- Marked as answer by kclark_clearp Thursday, July 16, 2009 9:23 PM
Thursday, July 16, 2009 5:21 PM
All replies
-
Hi,
I might be wrong, but you may be using the wrong plugin...
In order for LMeeting to work with OCS 2007 R2, you do not need the LM Outlook Plugin, but the Conferencing Add-On for Outlook and the LM client setup.
If you have installed the LM Plugin for Outlook, it will not work with OCS, but with MS Live Meeting service instead...
The downloaded files should be Confaddins_Setup.exe and LMSetup.exe instead of LMAddinPack.msi ...
BR
GeorgeFriday, July 10, 2009 8:15 AM -
I believe I've found the issue. The only content under the /Conf/Ext and /Conf/Int virtual directories is "TShoot.html". This is the case for both of my Front-end servers. Webconference validation succeeds, so I'm confused. Should there be content under these directories?Wednesday, July 15, 2009 3:40 PM
-
Is there any way to re-install the web components? It's clear I'm missing most of them. Trying to login to the conference site (internal or external) yields the error below. I have no "login.aspx" under the path shown, or any other files other than "TShoot.html."
Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /conf/int/login.aspxThursday, July 16, 2009 1:07 PM -
So before you rebuild the whole thing. Can you check to see what the internal URL is that it is handing out for conferences? and be sure that it is not trying to hit the wrong server or something.
as far as reinstalling the webcomponents you can do a reinstall but not sure if it will take things completly down during that time frame. If it is truly that messed up I would think about doing a complete re-install.
Mitchr |MCITP:Enterprise Server Admin, Messaging |MCTS:OCS with Voice Achievement |MCTThursday, July 16, 2009 2:20 PM -
I'm not sure I can answer your question. I cannot schedule a conference. I can use "Meet Now" in the MOC client, but trying the webURL (which I pulled from the OCS MMC) gives me the response above, and the Conference plug-in for Outlook will not log in (which I suspect is yet another symptom of the same problem). I do have two front-end servers, so I could take one down without bringing the whole environment down if a rebuild is necessary. Both are showing the same problem, though.Thursday, July 16, 2009 2:25 PM
-
if you can log in with Meet now then you should not have to rebuild.
So on your outlook, Go to the conferencing menu at the top. select User Accounts, check to see that your sip address is in the first box and is correct, there shouldn't be anything in any of the other boxes. Then click on Test connection. Let me know what that says once you have completed those steps.
thanks.
Mitchr |MCITP:Enterprise Server Admin, Messaging |MCTS:OCS with Voice Achievement |MCTThursday, July 16, 2009 2:41 PM -
Thanks Mitchr. I have never been able to log in via this method. My SIP URI is present, but the error after hitting "Test Connection" is "Cannot connect to server because the information in the User Accounts dialog might be incorrect or improperly formatted. Please verify that this information is correct, and then click Test Connection."
I am testing this from a machine that is not part of the domain, and have tried this both internally and externally (Edge). I should also note I've tried from a domain-member PC as well with the same results.
I found a support article stating this occurs due to an older version of the Conference add-in to Outlook, but I've confirmed I have the latest version. Haven't had any luck narrowing it down beyond that article.
-KevinThursday, July 16, 2009 3:07 PM -
OK so when you are on that page where your USER SIP URI is. Click on advanced. once in advanced then add your user name and password in place and check the box to use it. If that does not fix it. Specify the server names in the correct fields for internal put the fqdn:5061
for the external one put fqdn:443 the external fqdn should be your Access edge server which is usually sip.domain.com, the internal fqdn should be your pool fqdn then:5061
Let me know if that works. I am just asking you to test this. so we can determine next steps. I have a list of other things that cause this but I start with easiest first.
thanks.
Mitchr |MCITP:Enterprise Server Admin, Messaging |MCTS:OCS with Voice Achievement |MCT- Proposed as answer by Mitch Roberson Thursday, July 16, 2009 8:48 PM
- Marked as answer by kclark_clearp Thursday, July 16, 2009 9:23 PM
Thursday, July 16, 2009 5:21 PM -
Your first suggestion worked. I thought I'd tried every option. I know I'd set the server and login manually, but I hadn't set ONLY the login, leaving the server to auto-discover. It connected and I'm able to pull up the Live Meeting Scheduling display now.
Thank you very much!Thursday, July 16, 2009 7:31 PM