RSS Feed
http://www.proexchange.be/backend.php

Available now


EBook =
Available now
Printed version =
Available now @ HCW.BE
More info, click here

Search



Modules
· Home
· Articles & Tutorials
· Forums
· Members List
· Private Messages
· Search
· Statistics
· Stories Archive
· Web Links
· Your Account

Who's Online
There are currently, 22 guest(s) and 0 member(s) that are online.

You are Anonymous user. You can register for free by clicking here

Languages
Select Interface Language:


 A/V Authentication Service can't be reached...due to a comma ;-)

Office Communications Server 2007 R2
PinsartP posted a very interesting question in our forums, too which I didn't have a reply (how do you correct a configuration done according to the books?). Question was forwarded by Peter to Microsoft, and he was kind enough to share the solution :-) tnx Peter

Here's a copy-paste from his reply in the forum:

"the problem was linked to.... a comma...

Here's the explanation:
For all of you European OCS 2007 R2 users, there’s a small “hidden feature” in the release of the OCS 2007 R2 Edge server. During our migrations from OCS 2007 R1 to the all new R2 RTM release, we noticed some stange A/V Edge Auhentication server errors. Users would see a “limited calling” error in Communicator, the Mediation server would complain there was no valid A/V Authentication service, and the front-end A/V Validation would simply fail without any helpfull notification. After some in-house troubleshooting, it was time to call in the troops. Together with Microsoft, we validated the Edge configuration, did some tracing, and couldn’t find anything wrong with the edge server. One of the problems that kept coming up was a vague “Version MisMatch” error in the snooper logs. One of our troops at Microsoft took a closer look and noted that the edge server was complaining about a version 2,0 instead of a 2.0. Yes, you read that correctly, a comma instead of a period. We never thought of the fact that we installed the servers with Dutch localization, and apparently, Microsoft didn’t either. One of the main differences when using a European localization, is the change in number notation. Where the US locale uses a notation like $ 1,000,000.00 , us Europeans will use € 1.000.000,00 . This caused the Edge server to be unable to recognize any version numbers coming in. This bug has been reported to Microsoft, and is in the process of being fixed.

In the meantime, you can work around this issue in the following manner;

On the Edge server, add the Edge Service account to local administrators and logoff. Logon using the Edge Service account Go to control panel, Regional and Language options. Change the format to English (US). Remove the Service Account from the local administrators and reboot. You can verify this workaround by rerunning the validation wizzard on your front-end. It will show the A/V authentication service pass with flying colours!"

- Ilse




 
Login
Nickname

Password

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Websites

Related Links
· More about Office Communications Server 2007 R2
· News by ivcrieki


Most read story about Office Communications Server 2007 R2:
OCS 2007 R2 Client Docs


Article Rating
Average Score: 0
Votes: 0

Please take a second and vote for this article:

Excellent
Very Good
Good
Regular
Bad


Options

 Printer Friendly Printer Friendly


"A/V Authentication Service can't be reached...due to a comma ;-)" | Login/Create an Account | 0 comments
The comments are owned by the poster. We aren't responsible for their content.

No Comments Allowed for Anonymous, please register
© 2006 Pro-Exchange. All rights reserved.