Microsoft Support

Page 41 of 907« First...102030...3940414243...506070...Last »

After you prepare the Active Directory forest for the installation of Live Communications Server, the Prep Forest command is available in the Live Communications Server Deployment Tool

You prepare the Active Directory directory service schema and the Active Directory forest for the installation of Microsoft Office Live Communications Server 2005 or of Microsoft Office Communications Server. When you try to install Live Communications Server 2005 or Communications Server, you may experience one or both the following symptoms:
  • When you run the Microsoft Office Live Communications Server Deployment Tool to install or to activate Live Communications Server, the following symptoms occur:
    • The Prep Forest command is available (it does not appear dimmed).

      Note You do not expect this command to be available because you have previously prepared the Active Directory forest for the installation of Live Communications Server 2005 or of Communications Server.  

    • The Activate edition_type Server command is not available even if you have previously installed the Live Communications Server files.

      In this command, edition_type is the Live Communications Server edition that you want to activate. For example, replace edition_type with Standard Edition.

  • When you try to activate the Communications Server computer by using the LcsCmd.exe command-line tool, you receive the following error message:

    0xC3EC7826 The domain is not prepared to host LC Servers. Please ensure both forest and domain have been prepared and access to global settings container has been granted by DomainAdd task.

This issue occurs if Active Directory has been upgraded from Microsoft Windows 2000 Server to Microsoft Windows Server 2003. In this situation, you must perform the forest preparation operation again to create Communications Server-specific display specifiers for the Windows Server 2003 inetOrgPerson user type.

The inetOrgPerson user type was introduced in Windows Server 2003. When you run the LiveCommunications Server Deployment Tool, the Deployment Tool examines Active Directory to determine whether the forest preparation operation has been completed successfully. When the Deployment Tool determines that the inetOrgPerson user type does not have Live Communications Server attribute values set, the Deployment Tool determines that forest requires preparation for the installation of Live Communications Server 2005 or of Communications Server.

Note The Live Communications Server Setup program treats the inetOrgPerson user type the same as user type objects and contact type objects.

To work around this issue, click Prep Forest in the Live Communications Server Deployment Tool. Do this to prepare the Windows Server 2003 forest for the installation of Live Communications Server 2005 or of Communications Server. 
For more information about how to deploy Live Communications Server 2005, see the Live Communications Server Deployment Resources. To obtain the Live Communications Server Deployment Resources, visit the following Microsoft Web site:

Article ID: 898516 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communications Server 2007 Enterprise Edition
  • Microsoft Office Communications Server 2007 Standard Edition
  • Microsoft Office Live Communications Server 2005 Enterprise Edition
  • Microsoft Office Live Communications Server 2005 Standard Edition
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
kbnosurvey kbarchive kbinfo kbprb kbtshoot KB898516

See original article:
After you prepare the Active Directory forest for the installation of Live Communications Server, the Prep Forest command is available in the Live Communications Server Deployment Tool

When you try to establish a data-sharing session through Microsoft Office Communicator 2005, you may receive an error message

When you try to establish a data-sharing session through Microsoft Office Communicator 2005, you may receive the following error message:

Cannot establish the data sharing session with Buddy_name, either because Buddy_name canceled the sessionor because you or the person you are calling is behind a firewall or Network Address Translator (NAT).

This issue may occur when the computer uses an UPnP™ certified Network Address Translation (NAT) device.

Typically, a single Session Initiation Protocol (SIP) port is required for data sharing through a NAT device. However, an UPnP certified NAT device requires two SIP ports to establish a data-sharing session. Communicator 2005 only uses a single SIP port for data sharing. It does not support data sharing through an UPnP certified NAT device.

Article ID: 899568 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communicator 2005
kbnosurvey kbarchive kbplugplay kbrtc kbnat kbtshoot kbprb KB899568

Visit site:
When you try to establish a data-sharing session through Microsoft Office Communicator 2005, you may receive an error message

Anonymous users can send instant messages under the display name of authenticated users in Office Communications Server 2007 R2

Consider the following scenario:
  • In Microsoft Office Communications Server 2007 R2, an anonymous user uses a display name that is the same
    as the display name of an authenticated user.
  • The anonymous user joins a conference.
  • The
    authenticated user joins the same conference and then sends an instant message in the
    conference.
  • The anonymous user sends an instant message.

In
this scenario, the
instant
message that is sent by the anonymous user appears
in the conversation window of all the participants who are listed
under the user
name of the authenticated user,
just as if this instant
message was sent by the authenticated
user.

To
resolve this issue, apply the following update:
969824

(http://support.microsoft.com/kb/969824/
)

Description of the update package for Office Communications Server 2007 R2, Communicator Web Access: July 2009

Article ID: 972711 – Last Review: January 9, 2015 – Revision: 3.0


Applies to
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
kbnosurvey kbarchive atdownload kbexpertiseinter kbsurveynew kbprb KB972711

Read More:
Anonymous users can send instant messages under the display name of authenticated users in Office Communications Server 2007 R2

Presence information does not work for approximately 30 minutes after you log on Communicator Web Access 2007 R2

After you log on Microsoft Office Communicator Web Access
2007 R2, the presence information does not work for approximately 30 minutes.
This issue occurs if the registry entry

fipsalgorithmpolicy

is
set to 1 under the following registry subkey:

HKEY_LOCAL_MACHINESystemCurrentControlSetControlLSA

To resolve this issue, apply the following update:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

970679

(http://support.microsoft.com/kb/970679/
)

Description of the update package for Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core Redist 64-bit: July 2009

Article ID: 972702 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
kbnosurvey kbarchive atdownload kbexpertisebeginner kbsurveynew kbprb KB972702

See the article here:
Presence information does not work for approximately 30 minutes after you log on Communicator Web Access 2007 R2

Error message when a SIP message request is sent from a federated partner in Communications Server 2007 R2: “500: Server Internal Error”

When a federated partner sends a Session Initiation Protocol
(SIP) message request, Microsoft Office Communications Server 2007 R2 returns
the following generic SIP error
message:

500: Server
Internal Error

The SIP
stack implementation of
the federated partner does not copy the EPID parameter
from the “To” header of the 200 OK message to the “To” header of the ACK
message.
To
resolve this issue, apply the following update:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

969821

(http://support.microsoft.com/kb/969821/
)

Description of the update package for Office Communications Server 2007 R2: July, 2009

Article ID: 972709 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
kbnosurvey kbarchive atdownload kbexpertiseinter kbsurveynew kbprb KB972709

See the original article here:
Error message when a SIP message request is sent from a federated partner in Communications Server 2007 R2: “500: Server Internal Error”

When Office Communications Server 2007 R2 routes a voice mail call to an Exchange Server 2007 Unified Messaging server, the corresponding invitation message does not indicate that the request originates from Office Communications Server

When
Microsoft Office Communications Server 2007
R2 routes a voice mail call to a Microsoft
Exchange
Server 2007 Unified Messaging server, there is no
indication in the corresponding invitation message
that the request originated from Office Communications Server. However, the
Exchange Server
2007 Unified
Messaging server may require this information to
perform additional processing for requests
that originated from Office Communications Server.

To
resolve this issue, apply the following update:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

969821

(http://support.microsoft.com/kb/969821/
)

Description of the update package for Office Communications Server 2007 R2: July, 2009

Article ID: 972700 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
kbnosurvey kbarchive atdownload kbexpertiseinter kbsurveynew kbprb KB972700

View post:
When Office Communications Server 2007 R2 routes a voice mail call to an Exchange Server 2007 Unified Messaging server, the corresponding invitation message does not indicate that the request originates from Office Communications Server

Description of the Access 2003 hotfix package (Msaccess.msp): June 30, 2009

This article describes the Microsoft Office Access 2003 issue that is fixed in the hotfix package that is dated June 30, 2009.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must have Office 2003 Service Pack 3 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

870924

(http://support.microsoft.com/kb/870924/EN-US/
)

How to obtain the latest service pack for Office 2003

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This P1 may not contain all the files that you must have to fully update a product to the latest build. This P1 contains only the files that you must have to correct the issueP2 that P3 listed in this article.

The P1 version of this P2 uses a Microsoft Windows Installer package to install the P2. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Checksigned.log Not Applicable 185 23-Jun-2009 17:07 Not Applicable
Office2003-kb972557-glb.exe 11.0.8312.0 3,713,416 23-Jun-2009 17:02 x86
Msaccess.cab Not Applicable 17,072,993 23-Jun-2009 17:05 Not Applicable

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Msaccess.msp Not Applicable 44,772,352 23-Jun-2009 17:00 Not Applicable

Msaccess.msp information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Msaccess.exe 11.0.8312.0 6,699,864 22-Jun-2009 21:16 x86
Msaexp30.dll 11.0.8153.0 136,032 16-Jan-2007 20:32 x86
Mscdm.dll 11.0.8204.0 238,080 14-Dec-2007 19:47 x86
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 972557 – Last Review: January 9, 2015 – Revision: 1.0


Applies to
  • Microsoft Office Access 2003
kbnosurvey kbarchive kbsurveynew kbexpertiseinter kbqfe kbhotfixrollup kbautohotfix kbHotfixServer KB972557

Read the original post:
Description of the Access 2003 hotfix package (Msaccess.msp): June 30, 2009

You may receive an error message when you try to convert a Microsoft Access 2000 or a later version database to a Microsoft Access 97 database

When you try to convert a Microsoft Access 2000 or a later version database to a Microsoft Access 97 database, you may receive the following error message:
This problem may occur if your database contains the Number data type. Then, the Number data type must have the Field Size property set to Decimal.
To resolve this problem, change the Field Size property for the Number data type from Decimal to Double.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

For additional information about new database features, click the following article number to view the article in the Microsoft Knowledge Base:

275561

(http://support.microsoft.com/kb/275561/
)

Description of the new features that are included in Microsoft Jet 4.0

Article ID: 887032 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Access 2003
  • Microsoft Access 2002 Standard Edition
  • Microsoft Access 2000 Standard Edition
  • Microsoft Access 97 Standard Edition
kbnosurvey kbarchive kbconversion kberrmsg kbtshoot kbprb KB887032

Visit site:
You may receive an error message when you try to convert a Microsoft Access 2000 or a later version database to a Microsoft Access 97 database

The Attendant Console does not correctly process incoming voice calls if the Microsoft Office Communications Server 2007 R2 Attendant is configured to start automatically in General Options

The Microsoft Office Communications Server 2007 R2 Attendant
is configured to start automatically in General Options. In this situation, Microsoft Office Communicator 2007 R2 starts
and runs successfully. However,
the Attendant Console does not correctly process incoming voice calls.
This
problem occurs when Office Communications Server 2007 R2 Attendant and Office
Communicator 2007 R2 both run at the same time. Each client process is expected
to create a mutex in memory. When the mutex from the first process is
detected, this is expected to force the second client process to close during startup. If Microsoft Office Communications Server 2007 R2 Attendant is configured to start automatically in General Options, a mutex is not created. This enables Microsoft Office Communicator 2007 R2 to run at the same time.

If
Microsoft Office Communications Server 2007 R2 Attendant is configured to start
automatically in
General Options, a mutex is not created. This enables Microsoft Office
Communicator 2007 R2 to run at the same time.

To work around this issue, do not configure Microsoft Office
Communications Server 2007 R2 Attendant to start automatically in General
Options
. Start the
program manually,
or copy a shortcut to Attendant
into the Startup folder.

Note
The
Startup folder is located under Programs on the Start menu.

To resolve this issue, install the following update:
970275

(http://support.microsoft.com/kb/970275/
)

Description of the update package for Communications Server 2007 R2, Attendant: June 2009

Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

Article ID: 972402 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communications Server 2007 R2 Standard Edition
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
kbnosurvey kbarchive kbfix kbqfe kbexpertiseinter kbsurveynew kbprb KB972402

Continue reading here:
The Attendant Console does not correctly process incoming voice calls if the Microsoft Office Communications Server 2007 R2 Attendant is configured to start automatically in General Options

An update package enables Office Communications Server 2007 R2, Mediation Server to include a diversion header in the re-invite after the server processes a 302 redirection

This article discusses an update package for Microsoft Office Communications Server 2007 R2, Mediation Server. This update enables Mediation Server to include a diversion header in the re-invite after the server processes a 302 redirection.

For more information about the update package for Office Communications Server 2007 R2, Mediation Server, click the following article number to view the article in the Microsoft Knowledge Base:

969835

(http://support.microsoft.com/kb/969835/
)

Description of the update package for Office Communications Server 2007 R2, Mediation Server: July 2009

Article ID: 972770 – Last Review: January 9, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
kbnosurvey kbarchive kbqfe kbexpertiseinter kbsurveynew KB972770

Read More:
An update package enables Office Communications Server 2007 R2, Mediation Server to include a diversion header in the re-invite after the server processes a 302 redirection

Page 41 of 907« First...102030...3940414243...506070...Last »

Recent Comments

    Archives

    Categories