Page 434 of 951« First...102030...432433434435436...440450460...Last »

Known issues that occur with public instant messaging and Lync Server or Communications Server

This article describes the known issues that occur when Live Communications Server 2005 with SP1, Office Communications Server 2007, Office Communications Server 2007 R2, Lync Server 2010 and Lync Server 2013 are configured for public instant messaging (IM) with any of the three available public Internet connectivity (PIC) IM service providers.

Note This article also lists the known IP addresses that are used by
each public IM service provider.

This
article outlines the known issues that can occur when PIC IM connectivity is
configured by using one of the following three public IM service providers:

  • AOL
  • MSN (Windows Live), The Microsoft Network
  • Yahoo!

Note The
issues that are described in this article discuss the supported functionality
of the public IM service providers’ clients and data centers. Issues that are
centric to the public IM service providers’ clients and data centers are not
related to the required updates for the Microsoft Communications Server
products that are described in Applies To section of this document.

Note For details on PIC federation and Yahoo Messenger, read the Public Instant Messaging Connectivity section of the following Microsoft TechNet article:

Planning for SIP, XMPP Federation and Public Instant Messaging

(http://technet.microsoft.com/en-us/library/jj204825.aspx)

General issues and functionality overview

You should know
about the following issues that apply to all clients:

  • Public
    IM connectivity supports only the exchange of IM and presence information. File
    transfers, audio, video, or other sessions are not supported. This applies to
    all public IM service providers and all clients.

    Note For details on peer to peer A/V communications between Windows Live Messenger and Lync 2013 federated clients, read the Public Instant Messaging Connectivity section of the following Microsoft TechNet article:

    Planning for SIP, XMPP Federation and Public Instant Messaging

    (http://technet.microsoft.com/en-us/library/jj204825.aspx)

  • When a Lync user, a Communicator user or a Windows Messenger 5.1 user adds an MSN (Windows Live) contact, a Yahoo! contact, or an AOL contact, no verification is performed against the contact name. Therefore, if a user enters an invalid contact, it is added to the contact list and appears with an “Offline” status
  • When a Lync user or Communicator user is in a meeting, their status is displayed as “Online” to MSN (Windows Live) contacts, to AOL contacts, and to Yahoo! contacts. Lync users or Communicator users must manually set their status to the “Busy” status if they do not want their status to appear as “Online.”
  • Multiparty IM (MIM) is not supported. Users in a Lync server or Communications server environment can only have one-to-one communication with users of the public IM service providers.
  • The traffic between the Lync server or Communications server organizations and the public IM service provider is encrypted. IT administrators can set up Transport Layer Security (TLS) to encrypt the data that goes from the enterprise user’s client to the Lync server or Communications server. However, the data that goes from the public IM service providers’ server to the public IM client (on the MSN (Windows Live) network, the Yahoo! network, or the AOL network) is not encrypted. 

    Note An
    exception to this rule is the fact that data from AOL Instant Messenger 6.0,
    later versions of AOL Instant Messenger, and AOL Instant Messenger Professional
    Edition is sent through an encrypted channel by using Secure Sockets Layer
    (SSL).

  • If you are using the multiple points of presence (MPOP) feature with Lync clients or Communicator clients, presence updates may not appear in the MSN (Windows Live), AOL, or Yahoo! client, depending on the priority of the presence states on the various endpoints.
  • As
    with federated users, you can only see presence information about public IM users
    who are in your contact list. Additionally, these users can see presence
    information in Microsoft Office programs.
  • Friendly names of MSN (Windows Live), of AOL, or of Yahoo! users will not appear in the Windows Messenger 5.1 SIP client, Communicator clients or Lync clients

Supported clients

Public IM connectivity works with the following clients:

  • AOL client versions: AOL version 5.9.3702 and later
    versions
  • MSN (Windows Live) clients and versions: MSN Messenger 6.2
    and later versions and Windows Live Messenger 8.0 and later versions
  • Yahoo! client version: Yahoo! Messenger 6.0.0.1750 and later versions
  • Communications Server clients: Windows Messenger 5.1, Communicator 2005, Communicator 2007, and Communicator 2007 R2
  • Lync Server clients: Lync 2010 and Lync 2013

Supported public IM domains

The following is a list of currently supported public IM domains:

  • AOL

    • aol.com
    • icq.com – As of June 10, 2011 ICQ was disconnected pursuant to AOLs sale of ICQ to Digital Sky Technologies (DST).
    • love.com
    • mac.com
  • MSN (Windows Live)
    • br.live.com 
    • hotmail.co.il
    • hotmail.co.jp 
    • hotmail.co.th
    • hotmail.co.uk
    • hotmail.com
    • hotmail.com.ar
    • hotmail.com.tr
    • hotmail.es
    • hotmail.de
    • hotmail.fr
    • hotmail.it 
    • hotmail.ch
    • live.at
    • live.be
    • live.ca
    • live.cl
    • live.cn
    • live.co.in
    • live.co.kr
    • live.co.uk
    • live.co.za
    • live.com
    • live.com.ar
    • live.com.au
    • live.com.co
    • live.com.mx
    • live.com.my
    • live.com.pe
    • live.com.ph
    • live.com.pk
    • live.com.pt
    • live.com.sg
    • live.com.ve
    • live.de
    • live.dk
    • live.fr
    • live.hk
    • live.ie
    • live.in
    • live.it
    • live.jp
    • live.nl
    • live.no
    • live.ph
    • live.ru
    • live.se
    • livemail.com.br
    • livemail.tw
    • messengeruser.com
    • msn.com
    • outlook.com 
    • passport.com 
    • sympatico.ca
    • tw.live.com 
    • webtv.net
    • windowslive.com
    • windowslive.es
  • Yahoo

Issues with public IM connectivity to MSN (Windows Live)

The following is a list of the issues that a user may experience
when a public IM is connected to MSN (Windows Live):

  • In the case that the public IM connectivity becomes unavailable, presence
    information may be invalid for as long as four hours. To resolve this issue,
    log off and then log back on.
  • The “Be Right Back” status maps to the “Away” status when Lync users or Communicators users and MSN Messenger users view one another’s presence.
  • When an MSN (Windows Live) user’s status is set to “Out to Lunch,” it is displayed as “Away” on the Lync client or Communicator client because Lync client or Communicator does not support the “Out to Lunch” status. 
  • When a Lync user or Communicator user’s status is set to “Do Not Disturb,” it is displayed as “Away” on the MSN (Windows Live) client because the MSN (Windows Live) client does not support the “Do Not Disturb” status.
  • Lync server or Communications server contacts are blocked when MSN (Windows Live) users remove themselves from a contact list.
  • If you already had contact e-mail addresses in your contact list before you switched your contact list from the .NET Messenger Service to the Lync server or Communications server environment by using public IM connectivity, these contacts may continuously appear with an “Offline” status. These contacts are currently still associated with the .NET Messenger Service. You must delete and re-add the e-mail address to your contact list to associate the contact with the Lync server or Communications server front end service.
  • Friendly names of offline MSN (Windows Live) contacts will
    not appear.

Client-specific issues


Issues with public IM connectivity to Office Communicator clients

  • In versions of MSN Messenger that are earlier than Windows Live Messenger 8.0, if a MSN Messenger user opens a conversation window together with a Lync user or Communicator user for any reason, a toast or a conversation window will open for the Lync user or Communicator user. This issue occurs regardless of whether the MSN Messenger user types or uses the conversation window or session. 
  • As of October 11, 2005, all EASI Windows Live ID domains are fully supported for the Public IM Connectivity (PIC) service. This means that Lync users or Communicator users can communicate with MSN (Windows Live) users by using EASI Windows Live IDs through PIC. 

    EASI ID enables MSN (Windows Live) users to use the domain name of their choice to create an IM address through Windows Live ID. For example, a user’s EASI Windows Live ID could have been username@contoso.com . This was a great service for MSN (Windows Live) users. However, the service caused problems when PIC-enabled users tried to communicate with MSN (Windows Live) users by using Lync or Communicator.

    With the change of October 11, 2005, you can use the EASI Windows Live ID with PIC by making a simple change when you add a user to your Lync or Communicator contact list. A Lync user or Communicator user who wants to add the EASI Windows Live ID of username@contoso.com would add the following address to the search field: 

    username(contoso.com)@msn.com

    This
    increases the effectiveness of the PIC service because contacts who have
    unsupported EASI Windows Live ID domains no longer have to change their domains
    in order to use the PIC Service.

Issues with public IM connectivity to MSN Messenger

  • If
    a MSN (Windows Live) client starts a file transfer, other sessions, such as
    Audio and Webcam, will not be canceled as expected by the public IM
    connectivity service. The MSN (Windows Live) user must manually cancel the
    request.
  • In MSN Messenger 6.x and MSN Messenger 7.0 Beta clients, the Lync 2010 client or Communicator client will receive the following message from the MSN Messenger client if there any unsupported features are started: invited you to view his or her webcam. This requires the latest version of MSN Messenger. You can download the latest version at http://g.msn.com/5meen_us/122. Examples of unsupported features are a file transfer, an audio and video sessions, or an A/V. Ignore this message when you receive it. 

Note For details on peer to peer A/V communications between Windows Live Messenger and Lync 2013 federated clients, read the Public Instant Messaging Connectivity section of the following Microsoft TechNet article:

Planning for SIP, XMPP Federation and Public Instant Messaging

(http://technet.microsoft.com/en-us/library/jj204825.aspx)

Issues with public IM connectivity to AOL

  • When an AOL user sends a URL to a Lync user or Communicator user, the URL that is received by Lync user or Communicator is changed. For example, if an AOL user sends the URL http://www.contoso.com, the Lync user or Communicator user receives the following URL: _http://www.contoso.com_ (http:// www.contoso.com) 

Issues with public IM connectivity to Yahoo!

For details on PIC federation and Yahoo Messenger, read the Public Instant Messaging Connectivity section of the following Microsoft TechNet article:

Planning for SIP, XMPP Federation and Public Instant Messaging

(http://technet.microsoft.com/en-us/library/jj204825.aspx)

  • If a Lync user or Communicator user tries to establish a video session with a Yahoo! user and then cancels the session, the Communicator user is disconnected from the IM session.
  • When a Yahoo! user specifies that his or her presence should always appear offline or unavailable to a Lync client or Communicator client, the Lync client or Communicator client continues to see the Yahoo! user’s true presence
  • When a Lync user or Communicator user adds a Yahoo! user to his or her contact list, the Yahoo user clicks Allow to add the Lync user or Communicator user to the Yahoo user’s contact list. When the Lync user or Communicator user is added, the user’s status is displayed as offline until the Lync user or Communicator user changes his or her status.
  • During an IM session between a Lync user or Communicator user and a Yahoo! user, the Lync user or Communicator user is not notified. The Lync user or Communicator user can continue to send messages after the Yahoo! user closes the session window. 
  • The
    Yahoo! client does not support MPOP. If you connect to more than one device,
    all other devices show a status of “Unavailable” or of “Offline” to the Yahoo!
    client.
  • Yahoo! clients only support instant message invitations. However, if a Lync client or Communicator client sends a file transfer, an A/V invitation, or another invitation that is not supported for public IM connectivity, the Yahoo! client returns a 200 OK response that indicates acceptance. This response is displayed to the Lync user or Communicator user who is waiting for acceptance from the Yahoo! user. The Yahoo! user is not notified of this request. 
  • A Yahoo! client does not accurately maintain
    presence.

Windows root certificate information

For detailed information on Windows root certificates and updates for Windows root certificates review the following Microsoft KB article

931125

(http://support.microsoft.com/default.aspx?scid=kb;EN-US;931125)

Windows root certificate program members

Recommended firewall configuration

As documented in the deployment documentation for all versions of Lync server or Communications server , the recommended firewall configuration when federating with public IM providers is to enable any IP address to connect to port 5061 on the Access Proxy or Edge servers Remote Access interface. 
However, certain enterprises prefer to enforce stricter firewall rules and restrict incoming connections to specific IP addresses. In this case, the IP addresses that are used by the public IM networks have to be specifically enabled on the Lync server or Communications server’s perimeter networks external firewall. 

This article lists the IP
addresses that are used by each public IM service provider. Note that this list
may change. If there is a change to this list, a reconfiguration of the
enterprise firewall will be required. The following lists contain the IP
addresses that are currently used by each service provider.

IP addresses that are used by MSN (Windows Live)

  • 134.170.96.0/26
  • 157.56.187.192/26
  • 111.221.122.192/26

IP addresses that are used by AOL

IP addresses that are used by Yahoo!

  • 76.13.22.8 (host)
  • 76.13.22.9 (host)
  • 76.13.22.10 (host)
  • 76.13.22.11 (host)
  • 76.13.22.12 (vip)

    Primary colo:

  • 98.136.47.8 (host)
  • 98.136.47.9 (host)
  • 98.136.47.10 (host)
  • 98.136.47.11 (host)
  • 98.136.47.17 (vip)

The
third-party products that this article discusses are manufactured by companies
that are independent of Microsoft. Microsoft makes no warranty, implied or
otherwise, about the performance or reliability of these
products.

Article ID: 897567 – Last Review: May 26, 2013 – Revision: 24.1


Applies to
  • Microsoft Lync 2013
  • Microsoft Lync 2010
  • Microsoft Office Communicator 2007 R2
  • Microsoft Office Communicator 2007
  • Microsoft Office Communicator 2005
  • Microsoft Windows Messenger 5.1
  • 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 Standard Edition
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Lync Server 2010 Standard Edition
  • Microsoft Lync Server 2010 Enterprise Edition
  • Microsoft Lync Server 2013

Follow this link:
Known issues that occur with public instant messaging and Lync Server or Communications Server

Error message when you try to delete a company in Microsoft Dynamics GP or in Microsoft Great Plains: "Could not locate entry in sysdatabases for database ‘XXX’"

This article discusses that when you try to delete a company in Microsoft Dynamics GP, you receive the following error message:

MicrosoftODBC SQL Server DriverSQL ServerCould not locate entry in sysdatabases for database ‘XXX’. No entry round with that name. Make sure that the name is entered correctly.

This error message occurs when you delete the database in Microsoft SQL Server before you remove the company in Microsoft Dynamics GP or in Microsoft Great Plains.
To delete the company from Microsoft Dynamics GP, run the ClearCompanies.sql script. Click the following link to download the script:
https://mbs2.microsoft.com/fileexchange/?fileID=d57c52af-2432-486d-9072-e1a1d60563bf

(https://mbs2.microsoft.com/fileexchange/?fileID=d57c52af-2432-486d-9072-e1a1d60563bf)

To run the script, follow these steps depending on the SQL Server version you are using.

Microsoft SQL Server 2000

Run the script in Query Analyzer. To do this, follow these steps:

  1. Click Start, click Programs, point to Microsoft SQL Server, and then click Query Analyzer.
  2. In Query Analyzer, click File, and then Open.
  3. In the Open Query File window, locate and double-click the ClearCompanies.sql script that you downloaded in the “Resolution” section, and then click Open.
  4. Click Query, and then click Execute.

Microsoft SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012

Run the script in Studio Management. To do this, follow these steps:

  1. Click Start, point to All Programs, point to Microsoft SQL Server 2005 or Microsoft SQL Server 2008, and then click SQL Server Management Studio.
  2. In the Connect to Database Engine window, type the connection information, and then click Connect.
  3. Click New Query.
  4. Click File, point to Open, and then click File.
  5. In the Open File window, locate and double-click the ClearCompanies.sql script that you downloaded in the “Resolution” section, and then click Open.
  6. Click Execute.

Article ID: 863236 – Last Review: May 24, 2013 – Revision: 3.0


Applies to
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • System Manager
kbprb kbmbsmigrate KB863236

View the original here:
Error message when you try to delete a company in Microsoft Dynamics GP or in Microsoft Great Plains: "Could not locate entry in sysdatabases for database ‘XXX’"

How to remove a company that is no longer being used in Microsoft Dynamics GP

This article explains how to remove a company that is no longer being used in Microsoft Dynamics GP.

To remove a company that is no longer being used in Microsoft Dynamics GP, follow these steps:
  1. Follow the appropriate step:
    • If you are using Microsoft Dynamics GP 10.0 or later, click Tools on the Microsoft Dynamics GP menu, point to Utilities, point to System, and then click Delete Company.
    • If you are using Microsoft Dynamics GP 9.0, point to Utilities on the Tools menu, point to System, and then click Delete Company.
    • If you are using Microsoft Business Solutions – Great Plains 8.0, click Setup on the Tools menu, point to System, and then click Company.
    • If you are using a version that is earlier than Microsoft Business Solutions – Great Plains 8.0, click System on the Setup menu, and then click Company.
  2. Click the Company Name lookup.
  3. Click the company that you want to delete, click Select, and then click Delete.
  4. Verify that the company database was removed. To do this, follow the steps for the database that you are using with Microsoft Dynamics GP.

    Microsoft SQL Server 2005 / Microsoft SQL Server 2008 /Microsoft SQL Server 2008 R2 / Microsoft SQL Server 2012

    1. Start SQL Server Management Studio.
    2. Expand the instance of SQL Server for Microsoft Dynamics GP, and then expand Databases.
    3. Verify that the company database was removed. If the company database is listed, right-click the company database, and then click Delete.

    Microsoft SQL Server 2000

    1. Start Enterprise Manager.
    2. Expand the instance of SQL Server for Microsoft Dynamics GP, and then expand Databases.
    3. Verify that the company database was removed. If the company database is listed, right-click the company database, and then click Delete.

    Microsoft SQL Server Desktop Engine (MSDE)

    1. Start Support Administrator Console.
    2. Run the following command to verify that the company database still exists.
      SELECT name FROM MASTER..SYSDATABASES

    3. If the company database is listed, run the following command to delete the database.Note Replace XXX with the database name of the company that you want to delete.

  5. If the database has been manually removed or removed by the DROP script mentioned in step 4-c, then there may be some references from the deleted database still within the DYNAMICS/system database. These references need to be removed. To do this, download the ClearCompanies.sql script from the following link and then follow the steps:
    https://mbs2.microsoft.com/fileexchange/?fileID=d57c52af-2432-486d-9072-e1a1d60563bf

    (https://mbs2.microsoft.com/fileexchange/?fileID=d57c52af-2432-486d-9072-e1a1d60563bf)

    Microsoft SQL Server 2005 / Microsoft SQL Server 2008 / Microsoft SQL Server 2008 R2 / Microsoft SQL Server 2012

    1. Start SQL Server Management Studio.
    2. Click New Query from the menu bar to start a new query window.
    3. Paste the contents of the ClearCompanies.sql scripts into the empty query window.
    4. Click Execute or press F5 to run the script.

      Note ClearCompanies.sql is a script that is automatically setup to run against the appropriate databases.

    Microsoft SQL Server 2000

    1. Start Query Analyzer.
    2. Click Query and then click New Query to open a blank query window.
    3. Paste the contents of ClearCompanies.sql into this empty query window.
    4. Click on the ‘Execute’ button or press F5 to run the script.

      Note ClearCompanies.sql is a script that is automatically setup to run against the appropriate databases.

  6. Log into Microsoft Dynamics GP to verify the company no longer exists.

Article ID: 849249 – Last Review: May 24, 2013 – Revision: 6.0


Applies to
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • System Manager
kbhowto kbmbsmigrate KB849249

Originally posted here:
How to remove a company that is no longer being used in Microsoft Dynamics GP

Exchange Management Console (EMC) crashes, and you receive an error: "MMC could not create the snap-in"

When you try to start the Exchange Management Console (EMC) snap-in, you receive the following error message:

MMC could not create the snap-in.

MMC could not create the snap-in. The snap-in might not have been installed correctly.

Name: Exchange Server 2007

CLSID: FX:76dd58f7-54ba-42e3-a2e0-dbf4b674539f

Unhandled Exception in Managed Code Snap-in

FX:76dd58f7-54ba-42e3-a2e0-dbf4b674539f

Could not load file or assembly ‘Microsoft.Exchange.Management.SnapIn.Esm, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

Exception type: System.IO.FileLoadException

Exception stack trace:

at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)

at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

at System.Activator.CreateInstance(String assemblyName, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)

at System.Activator.CreateInstance(String assemblyName, String typeName)

at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)

at Microsoft.ManagementConsole.Internal.SnapInClient.CreateSnapIn(String assemblyName, String typeName)

at Microsoft.ManagementConsole.Internal.ClassLibraryServices.Microsoft.ManagementConsole.Internal.IClassLibraryServices.CreateSnapIn(String assemblyName, String typeName)

at Microsoft.ManagementConsole.Executive.SnapInInitializationOperation.OnStart()

at Microsoft.ManagementConsole.Executive.RunningOperationsTable.EnqueueOperation(Operation operation)

at Microsoft.ManagementConsole.Executive.StandAloneComponentData..ctor(SnapInRegistrationInfo info, Int32 bookkeepingId)

at Microsoft.ManagementConsole.Advanced.FrameworkSnapInFactory.Microsoft.ManagementConsole.Advanced.ISnapInFactory.CreateSnapIn(Int32 bookkeepingId, String snapInKey, Object& snapIn)

If you start the Exchange Management Shell (EMS) at a command prompt by running the cmdlet C:Program FilesMicrosoftExchange Serverbinexshell.psc1, you receive the following error message:

WARNING: The following errors occurred when loading console C:|Program FilesMicrosoftExchange Serverbinexshell.psc1:

Cannot load Windows Powershell snap-in Microsoft.Exchange.Management.Powershell.Admin because of the following error:

Could not load file or assembly ‘Microsoft.Exchange.Management.Powershell.Configuration, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856as364e35′ or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

Command “, ‘ C:Program FilesMicrosoftExchange Serverbinexshell.psc1′” could not be executed because some Windows Powershell snap-ins did not load.

This issue occurs when you used the Strong Name tool, SN.exe, to disable Strong Name validation. Strong Name is a technology that was introduced together with the .NET Framework for use with managed code. Because Exchange Server 2007 uses managed code, Strong Name must be enabled. Otherwise, services will fail.
To resolve this issue, you must re-enable Strong Name validation. To do this, you must use the Strong Name tool (Sn.exe) that is included with the .NET Framework Software Development Kit (SDK).

To do this, open a command prompt, type the following command, and then press Enter:

sn -Vr *

Note To check your current settings for Strong Name verification, use the following command:

sn -Vl

For more information about the .NET Framework SDK, go to the following Microsoft website: For more information about the .NET Framework security policy model, go to the following Microsoft Developer Network (MSDN) website: For more information about how to use the Strong Name tool (Sn.exe) to create an assembly in the .NET Framework SDK, click the following article number to view the article in the Microsoft Knowledge Base:
302340

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

How to create an assembly with a strong name in the .NET Framework SDK

Article ID: 979695 – Last Review: May 24, 2013 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
kbsnapin kbexpertiseinter kbsurveynew kbprb KB979695

Excerpt from:
Exchange Management Console (EMC) crashes, and you receive an error: "MMC could not create the snap-in"

Formula errors in Excel when list separater is not set correctly

When entering a formula an error will occur if trying to use a symbol that is not the default ‘list separator’ in the Windows Regional settings.

“We found a problem with this formula. Try clicking Insert Function on the Formulas tab to fix it, or click Help for more info on common formula problems.”

If the error occurs when you use a character to separate the arguments you expect to work and Excel will not accept it then this is typically caused by either or both of the following scenarios:
  • The list separator in Windows – Regional Settings does not match what is being typed for the Excel formula.
  • The ‘Use system separators’ option is set in Excel Advanced Options and does not match what is being typed for the Excel formula.

To workaround the error message follow the following steps:
1. Determine if ‘Use system separators’ is selected in Excel options. From the File menu select Options. Select Advanced. In the ‘Editing options’ group determine if ‘Use system separators’ is unselected. If it is unselected you can select it to have Excel use the Windows Regional settings or specify the ‘Thousands separator’ you want to use.

If the ‘Use system separators’ is enabled then look in the Region (Regional) Settings in the Windows Control Panel. The list separator is specified in the Additional settings.

2. Use the same character as the designated list separator in Windows settings when creating the formula(s).

3. Use the Reset button to reset the options to match the default for the selected country or modify the Windows List Separator to a different character (some special characters cannot be used).

Note: By default, Microsoft Excel uses the system separators that are defined in the regional settings in Control Panel. If you sometimes need to display numbers with different separators for thousands or decimals, you can temporarily replace the system separators with custom separators. To do that please follow the steps in the following article http://office.microsoft.com/en-us/excel-help/change-the-separator-for-thousands-and-decimals-HP003089676.aspx

(http://office.microsoft.com/en-us/excel-help/change-the-separator-for-thousands-and-decimals-HP003089676.aspx)

Note: The comma is the default list separator for US – English Locale.

More information

Changing the List separator in the Windows Region settings will affect the delimiter used when opening or saving a Comma-separated value (.csv) file as Excel utilizes the Windows list separator character for the delimiter in .csv files.

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: 2853427 – Last Review: May 23, 2013 – Revision: 1.0


Applies to
  • Microsoft Office Excel 2003
  • Microsoft Office Excel 2007
  • Microsoft Excel 2010
  • Microsoft Excel 2013

View the original here:
Formula errors in Excel when list separater is not set correctly

How to find a Web Presence Provider for your FrontPage 2000 Web

This article describes how to find a Web Presence Provider (WPP) to host
the Web that you created in Microsoft FrontPage on the Internet.

Several features of your Web require the FrontPage Server Extension to be
installed on the server hosting your Web. Some features may not function if
they are hosted on a server that does not support the FrontPage Server
Extensions.

How to see the latest list of WPP referrals

  1. Open a Web in FrontPage.
  2. On the File menu, click Publish Web.
  3. Click WPP’s.

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

151725

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

How to import Web content from a server without Front Page Extensions

Article ID: 196247 – Last Review: May 23, 2013 – Revision: 3.0


Applies to
  • Microsoft FrontPage 2000 Standard Edition
kbhowto kbhowtomaster KB196247

See the original article here:
How to find a Web Presence Provider for your FrontPage 2000 Web

OWA redirection and SSL offloading fail after you install an Exchange Server service pack

After you install a service pack on a server that is running Microsoft Exchange Server 2010 or Exchange Server 2007, you may experience one or more of the following issues:
This issue occurs if the “Require SSL” configuration option is enabled on the default website or virtual directory.

Note By default, the “Require SSL” configuration option is enabled on the default website when you install an Exchange Server service pack. Additionally, the “Require SSL” configuration is enabled on the virtual directories under the default website.

To resolve this issue, follow these steps:
  1. Start IIS 7 Manager.
  2. Select the default website, and then make sure that you are in Features View.
  3. Double-click SSL Settings.
  4. Click to clear the Require SSL check box.
  5. Run the IISRESET command.
  6. Repeat steps 1 through 5 for all virtual websites under the default website.
For more information about SSL offloading in Exchange Server 2010, go to the following Microsoft TechNet website:
For more information about issues that can occur when you use a third-party SSL offloader in an Exchange Server 2007 environment, click the following article number to view the article in the Microsoft Knowledge Base:
945453

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

You cannot log on to Outlook Web Access in an Exchange Server 2007 environment, and you receive an error message: “HTTP Error 403.4″

Article ID: 2839692 – Last Review: May 22, 2013 – Revision: 1.0


Applies to
  • Microsoft Exchange Server 2007 Service Pack 1
  • Microsoft Exchange Server 2007 Service Pack 2
  • Microsoft Exchange Server 2007 Service Pack 3
  • Microsoft Exchange Server 2010 Service Pack 1
  • Microsoft Exchange Server 2010 Service Pack 2
  • Microsoft Exchange Server 2010 Service Pack 3
kbsurveynew kbprb kbfix KB2839692

Read More:
OWA redirection and SSL offloading fail after you install an Exchange Server service pack

USB device is not recognized when you attach it immediately after your Windows XP-based computer resumes from standby or hibernation

When you plug a USB device into a Windows XP-based computer immediately after the computer resumes from standby or hibernation, the computer does not recognize the USB device. When this occurs, you receive the following warning message:

Unrecognized device has been found.

When the computer resumes from standby or hibernation, there is a five-to-ten-second period when the selective suspend feature of the USB driver interferes with detection of the new USB device. The time delay depends on the following factors:
  • Host controller hardware
  • Attached hubs
  • Attached devices
  • USB driver versions
  • Support for USB 2.0
  • Additional system hardware or configurations that may change the timing

For other causes that prevent a USB device from being detected, go to the “Similar Problems and Solutions” section to view related Microsoft Knowledge Base articles.

Unplug the USB device, and then plug the device back into the computer or hub. If your computer still does not recognize the device, go to the “Workarounds” section.
If your computer does not recognize the USB device, first try method 1 to work around this issue.

Method 1: Initiate recognition of the USB device by using Device Manager

To initiate recognition of the USB device by using Device Manager, follow these steps:

  1. Click Start, click Run, type Devmgmt.msc, and then click OK. The Device Manager window opens.
  2. Click to select your computer as the location for the scan.
  3. On the Action menu, click Scan for hardware changes.

    Windows XP recognizes the new device.

  4. Close the Device Manager window.

If this method resolves the issue, you are finished.

If this method does not resolve the issue, go to method 2.

Method 2: Disable power management of the USB hub

Note If you perform the following procedure, you may also reduce the battery life on a portable computer.

Use this method if method 1 does not work. To disable power management of the USB hub, follow these steps:

  1. Click Start, click Run, type Devmgmt.msc, and then click OK. The Device Manager window opens.
  2. Expand Universal Serial Bus controllers.
  3. Right-click a USB Root Hub in the list, and then click Properties. The USB Root Hub Properties dialog box is displayed.
  4. Click the Power Management tab.
  5. Click to clear the Allow the computer to turn off this device to save power check box, and then click OK.
  6. Repeat steps 3 through 6 for each USB Root Hub in the list.
  7. On the Action menu, click Scan for hardware changes.

    Windows XP recognizes the new device.

  8. Close the Device Manager window.

If this method does not resolve the issue, go to method 3.

Method 3: Restart the computer

To initiate recognition of the USB device, first unplug the USB device and restart the computer. Then, wait five to ten seconds before you plug the USB device into the computer or hub.
Windows XP recognizes the new device.

If this method does not resolve the issue, you might want to review the articles in the “Similar Problems and Solutions” section, or contact Support. For information about how to contact Support, visit the following Microsoft Web site:

Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.
If the methods in this article do not resolve the issue, try the troubleshooting steps offered in similar Microsoft Knowledge Base articles.

For more information about advanced troubleshooting tips for general USB problems, click the following article number to view the article in the Microsoft Knowledge Base:

310575

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

Advanced troubleshooting tips for general USB problems in Windows XP

For more information about how to troubleshoot unknown devices in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

314464

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

How to troubleshoot unknown devices that are listed in Device Manager in Windows XP

If these articles do not resolve the issue, visit the following Microsoft Web site for information about how to contact Support:

Article ID: 871233 – Last Review: May 22, 2013 – Revision: 4.0


Applies to
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Tablet PC Edition
  • Microsoft Windows XP Media Center Edition 2004
  • Microsoft Basic Optical Mouse
  • Microsoft Comfort Optical Mouse 1000
  • Microsoft Comfort Optical Mouse 3000
  • Microsoft Habu Laser Gaming Mouse
  • Microsoft IntelliMouse Explorer 4.0
  • Microsoft Laser Mouse 6000
  • Microsoft Natural Ergonomic Keyboard 4000
  • Microsoft Compact Optical Mouse 500 v2.0
  • Microsoft Comfort Curve Keyboard 2000
  • Microsoft Wireless Laser Desktop 6000 v2.0
  • Microsoft Mobile Memory Mouse 8000
  • Microsoft Natural Wireless Laser Mouse 6000
  • Microsoft Notebook Optical Mouse 3000
  • Microsoft Optical Mouse by Starck
  • Microsoft SideWinder Mouse
  • Microsoft Wireless IntelliMouse Explorer with Fingerprint Reader
  • Microsoft Wireless Laser Mouse 6000
  • Microsoft Wireless Laser Mouse 7000
  • Microsoft Wireless Laser Mouse 8000
  • Microsoft Wireless Notebook Laser Mouse 6000
  • Microsoft Wireless Notebook Laser Mouse 7000
  • Microsoft Wireless Laser Mouse 5000
kbresolve kbtshoot kbpowerman kbusb kbprb KB871233

Excerpt from:
USB device is not recognized when you attach it immediately after your Windows XP-based computer resumes from standby or hibernation

"The Windows Installer Service Could Not Be Accessed" error message when you install a program in Windows XP

oneMscomBlade,oneMsomNav,oneMscomFooter,

See more here:
"The Windows Installer Service Could Not Be Accessed" error message when you install a program in Windows XP

Description of Microsoft Product Activation

To reduce software piracy and to make sure that all Microsoft customers receive the product quality that they expect, Microsoft is now including product activation technology in several products. This article defines product activation and describes when and how to activate a Microsoft product. It also explains how to contact a Microsoft Product Activation Center and contains additional product activation resources.
Note Microsoft product activation telephone numbers are not listed in this article. There are many regional Microsoft Product Activation Centers worldwide. Use the Product Activation Wizard to make sure that you are routed to the correct regional Product Activation Center.

For more information about how to contact the Microsoft Product Activation Center, click the following article number to view the article in the Microsoft Knowledge Base:

950929

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

How to contact the Microsoft Product Activation Center

Microsoft uses product activation to reduce a form of piracy known as “casual copying” or “softlifting.” Casual copying occurs when people share software in a way that violates the Microsoft Software License Terms. For example, when a person buys Windows XP, that copy of Windows XP is primarily licensed for use on a single computer. Without the purchase of additional licenses, that copy of Windows XP may not be installed on additional computers. For example, if that copy of Windows XP were to be shared with another person and installed on that other person’s computer, that would constitute casual copying. However, with most software licenses, you are allowed to reinstall and activate the software on the same computer an unlimited number of times. To make sure that you are using your Microsoft software appropriately, see the Microsoft Software License Terms or the product use rights for more information about that specific product.

Casual copying accounts for a large part of the piracy losses that the software industry experiences. If software piracy were to be reduced, the software industry could invest much more money in product development, in product quality, and in product support. This would lead to better products and more innovation for customers.

How product activation works

Product activation is a simple, straightforward process that is completely software based. It requires no hardware add-ons or any other external tool. In most cases, the only information that is needed to activate a product is an installation ID, which is created by the software itself. The information that is collected during activation will not be used to personally identify the user.

If you activate your product over the Internet, product activation takes less than a minute. When you activate your product in this way, the product itself will do most of the work. Very little user effort is required. If you would rather activate your product over the telephone, you can do this by contacting the regional Microsoft Product Activation Center.

For more information about how to contact the Microsoft product activation Center, click the following article number to view the article in the Microsoft Knowledge Base:

950929

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

How to contact the Microsoft product activation Center

Important Product activation does not track users of Microsoft software in any way. Its sole purpose is to activate legitimate licenses for Microsoft software.

When to activate a Microsoft product

Software that is bought in stores or as part of a new computer that is sold by an OEM must be activated. As mentioned earlier, product activation is easy, and many users only have to activate a product one time during the life of the product. However, some products may have to be activated again if the product is moved to another computer or if significant changes are made to the computer on which the product is installed.

Note OEMs may activate the software at the factory before they deliver the computer to the customer.

To make activation convenient, Microsoft products do not have to be activated immediately after they are installed. You can start Microsoft Office up to 50 times before you have to activate it. For Microsoft Windows, you have 30 days from the first time that you use the operating system before you have to activate it.

How to activate a Microsoft product

To activate a Microsoft product, select either the Internet option or the telephone option in the Product Activation Wizard.

  • With Internet-based activation, Microsoft servers process the activation and activate the product.
  • With telephone-based activation, you activate your product by contacting a Microsoft Product Activation Center and following the steps that are provided by an automated telephone system or by a customer service representative.
    Important You should have your installation ID when you speak with a customer service representative. This ID is displayed in the product activation wizard.

    For more information about how to contact the Microsoft product activation Center, click the following article number to view the article in the Microsoft Knowledge Base:

    950929

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

    How to contact the Microsoft product activation Center

Web sites

For more information, visit the following Microsoft Web sites:

Microsoft Knowledge Base articles

For more information about how to contact a Microsoft Product Activation Center, click the following article numbers to view the articles in the Microsoft Knowledge Base:

950929

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

How to contact the Microsoft product activation Center

299840

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

How to use Sysprep with Windows product activation or Volume License media to deploy Windows XP

291997

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

How to activate Windows XP using an Unattend.txt file

300273

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

Cannot activate OEM edition more than once in Office XP

298088

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

How to obtain a Volume License key for Enterprise Editions of Office XP

293477

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

Information about the Microsoft Activation Wizard Privacy Policy for Visio

293466

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

Reduced functionality, missing menu commands, and unavailable features in Visio

293151

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

Description of the Office Activation Wizard

291983

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

Ports that are used by Windows product activation

299056

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

An error message is displayed when you run Windows product registration

289657

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

Out of Box Experience (OOBE) does not run after Setup completes

Article ID: 302806 – Last Review: May 22, 2013 – Revision: 17.0


Applies to
  • Customer Service and Support Information
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Starter
  • Windows Vista Ultimate
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
  • Microsoft Windows Small Business Server 2003 Premium Edition
  • Microsoft Windows Small Business Server 2003 Standard Edition
  • Microsoft Office Basic 2007
  • Microsoft Office Home and Student 2007
  • Microsoft Office Standard 2007
  • Microsoft Office Professional 2007
  • Microsoft Office Professional Plus 2007
  • Microsoft Office Ultimate 2007
  • Microsoft Office Word 2007
  • Microsoft Office Visio Standard 2007
  • Microsoft Office InfoPath 2007
  • Microsoft Office Publisher 2007
  • Microsoft Office Project Professional 2007
  • Microsoft Office Project Standard 2007
  • Microsoft Office PowerPoint 2007
  • Microsoft Office Outlook 2007
  • Microsoft Office OneNote 2007
  • Microsoft Office Excel 2007
  • Microsoft Office SharePoint Designer 2007
  • Microsoft Office Professional Edition 2003
  • Microsoft Office Access 2003
  • Microsoft Office Excel 2003
  • Microsoft Office FrontPage 2003
  • Microsoft Office Outlook 2003
  • Microsoft Office PowerPoint 2003
  • Microsoft Office Publisher 2003
  • Microsoft Office Small Business Edition 2003
  • Microsoft Office Basic Edition 2003
  • Microsoft Office XP Developer Edition
  • Microsoft Office XP Professional Edition
  • Microsoft Office XP Proofing Tools Standard Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002
kmcustomerservice kbresolve kbmsccsearch kbpubtypekc kbenv KB302806

Follow this link:
Description of Microsoft Product Activation

Page 434 of 951« First...102030...432433434435436...440450460...Last »

Recent Comments

    Archives

    Categories