Error Message That Dublicate Computer Name when Browsing a Computer from Network

I was receiving error message "You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again" when i want to access a computer from the network after configured network load balancing on windows (NLB) for OCS R2 Enterprise Edition.

Solution:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

Create a new REG_DWORD key "DisableStrictNameChecking" and set its value to "1", then Restart Server Service.

More: www.mshowto.org

Error Message while activating the Pool at OCS R2's Enterprise Edition

I got following error code while activating the Pool at OCS R2's Enterprise Edition

Failure [0xc3ec796c] Activating a Front End server with Monitoring Server or Archiving Server configured requires MSMQ service on the Front End server.

Solution:

I installed MSMQ at Enterprise Edition of OCS R2 and then run setup again.

More: www.mshowto.org

Error Code: 0xC3EC7A19 when add server to pool at OCS 2007's Enterprise Edition

I got following error message when add server to pool at OCS 2007 R2

Error Code:

Unable to access pool information. Possible reasons include inability to authenticate to the domain, WMI service Issues, lack of network connectivity and other system issues. (Error Code: 0xC3EC7A19)

Solution:

My Server which will be installed OCS R2 could not reach to DC through network, checked all network components (repair network adapters) and problem solved.

More: www.mshowto.org

Error Code: SIP/2.0 486 Busy Here (in debug session) while want to start Live Meeting

I get an error message which all client PC that run live meeting that is "SIP/2.0 486 Busy Here".

I just moved my users from old Front-end server to new Front-end server, no any change as different and then Communicator was working but live meeting wasn`t working. I researched in google but no any resolution and then i decided to start Debugging Session on my edge server and get error message that "SIP/2.0 486 Busy Here" in the debugging log.

I researched again on the internet but no any solution for me. I checked all Front-end and edge architecture and found problematic point in my port number.

I had used different port number for all edge role, e.g: my access edge role was using the port number 444 and web access role was using the port number 447 and i had forgetten to change this port numbers at my new Front-end Server.

I changed port number at my new front-end server as following:

Standard Edition Server --> New Front-End Server --> Right click --> Properties --> Web Conferencing Properties --> Web Conferencing Edge Server and then changed the correct port numbers.

Shortly:

Problem: Error Message that SIP/2.0 486 Busy Here in the debug log on Edge Server
Solution: Changing to correct port number on Front-End Server

More: www.mshowto.org

Error Message : Setup cannot create the required database tables. Contact your SQL administrator.

I have got following error message at the sccm installation.

SqlError: [42000][5847][Microsoft][ODBC SQL Server Driver][SQL Server]Execution of .NET Framework code is disabled. Set "clr enabled" configuration option and restart the server.
Error: Could not create assembly file.
Could not install CLR assemblies.
Setup cannot create the required database tables. Contact your SQL administrator.

Solution:

1. Explore "SQL Server 2005/Configuration Tools Surface Area Configuration" in your Start menu.
2. Select "Surface Area Configuration for Features"
3. You will find "CLR Integration" option, activate it and save.

More: www.mshowto.org

SCCM Installation Error Related SQL Admin Rights

I have got following error message during SCCM installation

The site server computer's machine account does not have Administrator's privileges on the SQL Server selected for site database installation. To install a Configuration Manager site, all servers must be in an Active Directory domain and the site server's machine account must have Administrator's privileges on the SQL Server.

Resolution: I have gave admin right for SCCM Machines account where on SQL Installed machine's local admins groups and problem solved.

More: www.mshowto.org