Mino – The UC Guy

Microsoft Unified Communications Blog

Archive for the ‘Common Errors’ Category

October 2008 Communicator Update

Posted by Mino on October 27, 2008

Description of the update for Communicator 2007: October 24, 2008

This update fixes the following issues:

Posted in Common Errors, communicator client, Miscellaneous | Tagged: , , , , , , | Leave a Comment »

A/V edge server doesn’t work from outside, and external users have problem using audio/video

Posted by Mino on October 13, 2008

 AV edge server requires external interface  that has a public IP address that can route onto the Internet, This Edge interface requires that its traffic to and from its Edge interface be routed with no NAT applied.

you have to assign A/V external interface with a public IP address(no NAT) and connect to check the issue.
The Edge external adapter should have three (publicly routable) IP addresses — access, a/v, and web conf, and in that case, you should want default gateway on external interface pointing to your ISP

If the access, WebConferening Edge server have internal IP and using NAT
while A/V Edge server uses public routable IP address, it will rises
problems in this configuration. If we have defined two gateways in the
routing table, when internet request is coming, we unable to route it to
the correct gateway and it will cause problem. Thus we can only configure
one gateway in this configuration.

To workaround this issue, please either assign another two public IP
addresses for Access and Web Conferencing Edge servers, or install the A/V
Edge server in a separate server.

If the issue persists,  perform the following steps to test the issue:
1. Make sure necessary ports are open correctly
Policy Rules
Local Port: 443 TCP (STUN/TCP)
Direction: Inbound and outbound STUN/TCP media communications
Remote Port: Any
Local IP: The internal IP address of the A/V Edge Server
Remote IP: Any IP address

Local Port: 5062 TCP (SIP/MTLS)
Direction: Outbound (For authentication of A/V users)
Remote Port: Any
Local IP: The internal IP address of the A/V Edge Server.
Remote IP: Any IP Address

Local Port: 3478 UDP (STUN/UDP)
Direction: Outbound (for internal users to send media to external users)
Remote Port: Any
Local IP: The internal IP address of the A/V Edge Server
Remote IP: Any IP Address
Note: If you are using ISA Server as your firewall, you must configure the
rule for send/receive

Following ports should be opened for A/V edge server external interface.
Local Port: 443 TCP (STUN/TCP)
Direction: Inbound (for external users access to media and A/V sessions)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server
Remote IP: Any IP Address

Local Port Range: 50,000-59,999 TCP (RTP /TCP)
Direction: Inbound/Outbound (for media transfer)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server. This IP address
must be a publicly routable IP address.
Remote IP: Any IP Address

Local Port: 3478 UDP (STUN/UDP)
Direction: Inbound (for external users connecting to media or A/V sessions)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server
Remote IP: Any IP Address
Note: If you are using ISA Server as your firewall, you must configure the
rule for send/receive

Local Port Range:  50,000-59,999 UDP (RTP/UDP)
Direction: Inbound/Outbound (for media transfer)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server. This IP address
must be a publicly routable IP address.
Remote IP: Any IP Address

2. Check the global setting
a. On the Front End Server, open Office Communications Server 2007.
b. In the console tree, right-click the Forest node, click Properties, and
then click Global Properties.
c. Click the Edge Servers tab.
d. Check the A/V Edge Servers, the listed value is ocsedge2007 with port
5062.

Posted in A/V Edge Server, Common Errors, Consolidated Edge | Tagged: , , , , , , , , | 4 Comments »

you are unable to enable the new user for the OCS on ADUC (Active Directory Users and Computers) after introducing the Windows Server 2008

Posted by Mino on October 13, 2008

If you have an existing Windows Server 2003 forest running Office
Communications Server, and upgrade any of its domain controllers to Windows
Server 2008, Office Communications Server will not work correctly; some UI
elements will disappear, and you will be unable to add more Office
Communication Server servers or pools. To resolve this issue, you simply
reissue the command to prep the Active Directory forest for Office
Communications Server.

To do so using the user interface, use the Prep Forest option of the
deployment tool

(for more information, see “Running Prep Forest” in the Microsoft Office
Communications Server 2007 Active Directory Guide).

To prep the forest using the command line, use the following command:

LcsCmd.exe /forest /action:ForestPrep

After doing this, please check if the issue still exists. For more
information, please view the URL below:

Windows Server 2008 Support
http://technet.microsoft.com/en-us/library/cc707718.aspx

Then please uninstall and reinstall  the OCS 2007 administrative tools on
the Windows 2008 domain controller. To do so, follow the steps below:

1. Insert the OCS 2007 installation CD media on the Windows Server 2008
domain controller .
2. Lunch the Installation and select to install the Administrative Tools.
3. After the Administrative Tools installation finished. Please check if you
could enable users for OCS 2007 from ADUC.

Reference:

Office Communications Server 2007 Document: Supportability Guide
http://www.microsoft.com/downloads/details.aspx?FamilyID=f8cc9b59-225f-425d-bd3a-e506396c6207&DisplayLang=en

Posted in Common Errors | Tagged: , , , , , , , , , | 1 Comment »

ConfigUpdatesServer.vbs script might result in the error “ERROR: OCS Common Files not found in registry”

Posted by Mino on October 12, 2008

During configuration of the OCS 2007 Software Update Service you need to run the ConfigUpdatesServer.vbs script. However running the script might result in the error “ERROR: OCS Common Files not found in registry”.

If you are using a 64-bit version of Windows 2003 the error can be caused by running the command with the 64-bit version of cscript and since OCS 2007 is not a native 64-bit application it stores its registry information in the 32-bit area of the registry.

To overcome the problem use the 32-bit version of cscript found in c:\windows\syswow64.

Posted in Common Errors | Tagged: , | Leave a Comment »

OCS Audio Conferencing Dropping some particitpants

Posted by Mino on October 12, 2008

sometimes Conferencing participants are dropped from Audio conference , there are known issues that is caused by McAfee  (HIPS software scans) and can be resolved by installing the latest patch.
If it is your case, please download and apply the latest HIPS version 7.0.0
patch by contacting the vendor company.

http://download.nai.com/products/naibeta-download/mhip/HIP_700_ReleaseNotes.html

Posted in Common Errors | Tagged: , , | Leave a Comment »

Error on Moving move a user from the Standard Pool to the Enterprise Pool “User being moved is not provisioned in the destination pool”

Posted by Mino on October 12, 2008

When we move users between two pools, it will read both backend database,
the problem can occur if we have problem reading the backend database
during the operation due to network, security factors. A quick way to solve
this issue is to force move the user and restore his contact list per the
following steps:

Step1: Backup and Export the user data on LCS 2005
1.    Backup the user data on LCS server.
As a precaution, we will backup the user data prior to attempting the
export/import process.
a.    On your LCS server, click Start, Run, type cmd and click OK.
b.    Navigate to the C:\Program Files\Microsoft LC 2005\Server\Support
location.
c.    Type the following:
dbbackup.exe /backupfile:BackupLCS2005
d.    Verify the Backup completes successfully.
2.    Export the user data from LCS server.
a.    Within the command prompt, navigate to <Live Communications Server
installation CD>\Support
b.    Type the following:
dbimpexp.exe /hrxmlfile:c:\SavedUserData.xml /user:user@domain.com
OR
dbimpexp.exe /import /hrxmlfile:rtcdata.xml (all the users)
c.    Verify the Export completes successfully.

Step2: Forcibly move the LCS user to the other pool.
When you perform the move operation, select “Force the user move if the
server or pool is unavailable”. Note, if you force the move, all the user
data is lost e.g. user’s contact list. In our case, let’s continue the
force move as we will soon restore the user’s contact list per the next
step.

Step3: Import user data to the other pool.
1. On the destination server, copy the previous SavedUserData.xml to local
disk.
2. Within the command prompt, navigate to <Live Communications Server
installation CD>\Support
3. To import the data, Type the following:
dbimpexp.exe /import /hrxmlfile:c:\SavedUserData.xml
4. Verify the Import completes successfully.
5. Now check whether the new moved users can log on LCS 2005 and also have
his contact list.

Posted in Common Errors | Tagged: , , | 2 Comments »

COMO Error “You must update your version of Communicator Mobile before you can sign in”

Posted by Mino on October 12, 2008

1. Check the Client Version Filter defined in your OCS environment (on all
Front End Servers and Access Edge Servers):
a) Go to the Start Menu > Programs > Office Communications Server 2007
b) Expand Standard/Enterprise Edition Servers node
c) Right Click on the pool node. Choose Application Properties > Client
Version Filter
d) In the Client Version Filter window, highlight the line with a reference
to CPE
You may now either
a. Update the version number to block 2.0.324.x and below
Note: You will have to update this if you want to control the version of
the client in use
Or
b. Delete the line with CPE 2.0.xxxx <= Block by clicking Remove.
Note: You will have no control over the version of the client in use
e) Apply your changes
f) Restart RTCSRV service
For the Access Edge server launch ClientVersionFilterConfig.exe under
\Program Files\Common Files\Microsoft Office Communications Server 2007

Detailed steps you can see Configuring Client Version Filtering
http://technet.microsoft.com/en-us/library/bb936607(TechNet.10).aspx

2. Apply latest OCS update package on your OCS front end server and reboot
the serve to test:
952783   Description of the update package for Communications Server 2007:
August 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;952783

Posted in Common Errors | Tagged: , , | 1 Comment »

x64 Bit and OCS

Posted by Mino on October 1, 2008

I faced problem in implementation Client Web Access server on windows 2003 R2 SP2.

The problem prevent client web access…first I thought it is configuration problem but when I checked the event viewer I saw that Error

ErrorID : 2274

Source : W3SVC-WP

This error on CWA server related to cwsauth.dll file that can’t be loaded.

I contact Microsoft for the error and got the following replay:

    Support for 64-bit Operating Systems

    Office Communications Server 2007 supports the following tested 64-bit configurations:

  • The 64-bit edition of SQL Server™ 2005 SP2 on the Back-End Database of an Enterprise pool or the Archiving and CDR database.
  • Running the 32-bit version of the Access Edge Server on 64-bit hardware with WOW (Windows on Windows) 64 mode on the 64-bit edition of Windows Server 2003 SP1 and later.
  • Running the 64-bit kernel driver component of the A/V Edge Server natively on 64-bit hardware plus the A/V Edge Server service component with WOW64 mode on the 64-bit edition of Windows Server 2003 SP1 and later.
  • Running the 32-bit version of Standard Edition server on 64-bit hardware with WOW64 mode on the 64-bit edition of Windows Server 2003 SP1 and later.

Like you see it does not give any answer for my problem.. Actually deploying OCS in X64 bit system is not the best practice since the setup for OCS and the console run under the WOW64 subsystem since they are 32bit programs.

I searched the internet and find more problems related to this problem

Comment : Deploy your OCS server in win X86 mode..It is better.

Aside:Actually, I think your situation has a better solution that solve X64 problem. I think it is known issue with application running in IIS in WOW64 mode.

If you check your Event Log entries, you will likely find several of the following entry, followed by another entry declaring that the Application Pool is being disabled.

Event Type: Error
Event Source: W3SVC-WP
Event Category: None
Event ID: 2274 

Description:
Could not load all ISAPI filters for site/service.

I think the reason why you are getting this event is straight forward:

  • On 64bit Windows, the “bitness” (i.e. 32bit or 64bit) of a process must match the bitness of the DLLs loaded by that process. In other words, a 64bit EXE can only load 64bit DLLs, and 32bit EXE can only load 32bit DLLs ( the problem of the cwsauth.dll file ).
  • By default, IIS6 on 64bit Windows runs with 64bit W3WP.EXE worker processes
  • .NET Framework 2 has ASP.Net implemented through 32bit ISAPI DLLs.

What is happening when OCS wizard install .NET Framework 2 on IIS6 on 64bit Windows is that while IIS6 runs W3WP.EXE as 64bit, you are configuring it to load some 32bit ISAPI DLLs. This does not work and leads to the event log entry. Since the ISAPI DLLs are loaded for every request, this failure immediately happens again and again, thus triggering the “Rapid Fail Protection” health monitoring check of IIS6. This leads to this Application Pool being taken offline .

One way to fix this issue is to:

  1. Change IIS6 run W3WP.EXE as 32bit
  2. *** IMPORTANT *** Then restart the CWA Application Pool that returns the error since it is stopped. You cannot fix any error without restarting the Application Pool.

Changing IIS6 to run W3WP.EXE as 32bit allows the 32bit ISAPI DLLs installed by .NET Framework 2 for ASP.NET to load and run inside of it. This is done by running the following commandline:

CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

This command switches IIS6 into running WOW64 (i.e. 32bit compatibility) mode on 64bit Windows on-the-fly so that IIS6 can immediately run 32bit ISAPI DLLs… unless that Application Pool is ALREADY returning 503 errors, in which case you MUST restart the Application Pool to have the bitness switch take effect. It makes sense because a 503 error means the Application Pool is offline and not running, so you must restart it to have setting changes take effect.

You can do this by either:

  • Restarting the Application Pool in question
  • Restarting IIS
    NET STOP W3SVC /y & NET START W3SVC
  • Reboot the server
    SHUTDOWN -r -t 0

Now, I cannot guarantee that this works for you because you may have other applications that must run as 64bit, in which case you have a conflicting need to simultaneously run 32bit and 64bit code in IIS6, which is not allowed.

See KB 895976 for more details.

Posted in Common Errors | Tagged: , , , | Leave a Comment »

OCS Failed during Forest Preparation ( Forest Prep. )

Posted by Mino on October 1, 2008

OCS Server Failed during forest Prepration although the domain prep worked fine.Reading the logs doesn’t turn up anything obvious in terms of what fields are not available.

Failure [0xC3EC78CA] At least one built-in display specifier object could not be found. Please make sure all display specifier objects were created successfully during DcPromo process by checking log files (%Windir%\Debug\Dcpromohelp.log and %Windir%\Debug\Csv.log).

Realizing that Prep Forest adds the required OCS containers, you may have a write error or you could have problems with your AD schema.

This issue may occur if the Display Identifiers object cannot be located in Active Directory. 

To solve this problem:

1-Click Start, click Run, type cmd in the Open box, and then click OK.

2- Type the following command, and then press ENTER:
csvde -i -f %windir%\system32\mui\dispspec\dcpromo.csv -c DOMAINPLACEHOLDER domain distinguished name (DN) -j %windir%\debug -k

                 * Replace domain distinguished name (DN) in the command with the DN of the domain, such as dc=domain_name,dc=local.

For more Info check Microsoft KB

Posted in Common Errors | Tagged: , , , | Leave a Comment »