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

#N/A error displayed in data field of PivotTable based on OLAP data source

All the items in a data field in your PivotTable display
the #N/A error.
This problem may occur when both of the following
conditions are true:

  • You have chosen one of the following settings in the
    Show data as list in the PivotTable Field dialog box:

    • Difference From
    • % Of
    • % Difference From
    • Running Total in
  • Your PivotTable is based on an Online Analytical Processing
    (OLAP) data source.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

Follow this link:
#N/A error displayed in data field of PivotTable based on OLAP data source

How to install the Excel 2002 Report Manager add-in and Template Wizard add-in in Excel 2003 and in Excel 2007

This article describes how to install the Microsoft Office Excel 2002 Report Manager add-in and the Template Wizard with Data Tracking add-in programs in Microsoft Office Excel 2003 and in Microsoft Office Excel 2007. Although these add-ins are no longer fully supported in Excel 2003 and in Excel 2007, you can still download and use them.
To install the add-ins in Excel 2003 and in Excel 2007, follow these steps:

  1. Exit Excel 2003 or Excel 2007 if it is running.
  2. Download the program that you want.

    To download the Microsoft Excel 2002 Report Manager add-in program, visit the following Microsoft Web site:

    To download the Microsoft Excel 2002 Template Wizard with Data Tracking add-in program, visit the following Microsoft Web site:To locate additional Excel 2002 add-ins, visit the following Microsoft Web site:

    To locate additional add-ins that are not included with Excel, click the following article number to view the article in the Microsoft Knowledge Base:

    288118 

    (http://support.microsoft.com/kb/288118/
    )
    Add-ins that are not included with Excel

    Note These additional add-ins include the following:

    • Access Links
    • Report Manager
    • Template Wizard with Data Tracking
    • ODBC Add-in (xlodbc.xla)

    After you click Download, click Save to save the file to a location on the hard disk drive.

  3. From the folder where you saved the file, use an extract program to extract the file. The Report Manager file is named Rptmgr.exe, and the Template Wizard file is named TMPLWIZ.EXE. For example, you can use the WinZip extract tool to extract the file. For more information about the WinZip extract tool, visit the following WinZip Web site:Notes

    Reports.xla file is extracted from Rptmgr.exe.
    WZTEMPLT.XLA file is extracted from TMPLWIZ.EXE.

  4. In the folder where you extracted the file to, right-click the Reports.xla file for Report Manager or the WZTEMPLT.XLA file for Template Wizard, and then click Copy.
  5. Paste the Reports.xla file into the Library folder that is located in the 2003 Microsoft Office system program folder or in the 2007 Microsoft Office system program folder.

    The default location of the Library folder for the 2003 Microsoft Office system:

    C:Program FilesMicrosoft OfficeOffice11Library

    The default location of the Library folder for the 2007 Microsoft Office system:

    C:Program FilesMicrosoft OfficeOffice12Library

    To paste the file, right-click inside the Library folder, and then click Paste.

  6. Start Excel 2003 or Excel 2007.
  7. In Excel 2003, click Add-Ins on the Tools menu.

    In Excel 2007, click Microsoft Office Button, click Excel Options, and then click Add-Ins. Click Excel Add-ins in the Manage list box, and then click Go.

  8. In the Add-Ins dialog box, click to select the Report Manager check box or the Template Wizard with Data Tracking check box, and then click OK.

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

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

Read the article:
How to install the Excel 2002 Report Manager add-in and Template Wizard add-in in Excel 2003 and in Excel 2007

Description of the update package for Office Communicator 2007: February 2012

This article describes the Microsoft Office Communicator 2007 issue that is fixed in the Office Communicator 2007 update package that is dated February 2012.

This article describes the following items about the update package:

  • The issues that the update package fixes.
  • The prerequisites for installing the update
    package.
  • Whether you must restart the computer after you install
    the update package.
  • Whether the update package is replaced by any other
    update package.
  • Whether you must make any registry changes.
  • The files that the update package contains.

Issue that this update package fixes

This update fixes the following issue:

  • 2665724 

    (http://support.microsoft.com/kb/2665724/
    )
    Office Communicator 2007 asks for authentication information when you use a smart card to unlock the computer

Update information

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

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

There are no prerequisites for installing this update.

Restart requirement

You have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

Registry information

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

File information

This hotfix may not contain
all the files that you must have to fully update a product to the latest build.
This hotfix contains only the files that you must have to resolve the issue
that listed in this article.

The
global version of this hotfix package uses a Microsoft Windows Installer
package to install the hotfix package. 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.

Collapse this tableExpand this table

File name File version File size Date Time Platform
Abbrdialtone Not Applicable 97,402 01/13/12 11:18 Not Applicable
Communicatorexe 2.0.6362.212 5,736,728 01/13/12 11:18 x86
Gdiplus 5.2.3790.4377 1,738,576 01/13/12 11:18 Not Applicable
Rtmpltfm_dll 3.0.6362.202 5,449,992 01/13/12 11:18 x86
Uccp_dll 2.0.6362.212 3,290,376 01/13/12 11:18 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

View the original here:
Description of the update package for Office Communicator 2007: February 2012

"Fixed objects will move" notice comes up repeatedly when filtering a range

Consider this scenario: You open an Excel 97-2003 format file in Excel 2010. The file contains a table area with autofilter applied. The table area contains cell comments. When you attempt to filter the range, you receive the message, “Fixed objects will move.” You click OK, but the message comes up again and again before Excel finally filters the table range.
This is a confirmed issue in Microsoft Excel 2010. Microsoft is currently investigating the cause.
There are two possible workarounds for this issue:

1. If you need to keep the file in Excel 97-2003 format, change the comments’ properties to move and size with cells. The following macro will set all comments in the workbook to move and size with cells:

Dim wksht As Excel.Worksheet
Dim wb As Excel.Workbook
Set wb = ActiveWorkbook

    For Each wksht In wb.Worksheets
        For Each cmt In wksht.Comments
           cmt.Shape.placement = xlMoveAndSize
        Next cmt
    Next wksht

End Sub

2. Save the workbook in Excel 2007-2010 format (XLSX, XLSM, XLSB).

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.

Link:
"Fixed objects will move" notice comes up repeatedly when filtering a range

Excel may experience an unhandled exception when attempting to call Chart.Activate in the Worksheet_PivotTableUpdate() event

Excel may experience an unhandled exception when the Worksheet_PivotTableUpdate() event executes.
If a developer is attempting to call the Chart.Activate() inside the Worksheet_PivotTableUpdate() event, this can cause the exception. To work around this issue a developer can use the Application.OnTime() function to perform the task in the future. For example, here is the code that can cause the issue:
Private Sub Worksheet_PivotTableUpdate(ByVal Target As PivotTable)
ThisWorkbook.Charts(1).Activate
End Sub

To work around this add another subroutine and call it from within the PivotTableUpdate() event using the Application.OnTime() function:

Private Sub Worksheet_PivotTableUpdate(ByVal Target As PivotTable)
  Application.OnTime Now()"Sheet1.testroutine"
End Sub

Sub testroutine()
    ThisWorkbook.Charts(1).Activate
End Sub

This will allow the Chart.Activate() to happen one second in the future.

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.

More:
Excel may experience an unhandled exception when attempting to call Chart.Activate in the Worksheet_PivotTableUpdate() event

Use the SetMailboxType command to modify mailbox size limits

What happens to an already provisioned mailbox when extensionAttributexx (the mailbox size value) is nullified or an incorrect character is specified?
Scenario 1
  1. The extensionAttributexx attribute is not set or is set incorrectly.
  2. Then, the attribute is updated to a value such as MBX=ST or MBX=DW.

In this scenario, the mailbox changes when this recognized and supported value is set.

Scenario 2

  1. The extensionAttributexx attribute is set to MBX=ST or to MBX=DW.
  2. Then, the attribute is cleared and set to null.

In this scenario, the mailbox remains at the previous size. 

There are two files that customize the processing of the SetMailboxType script:
  1. The input-config file includes the extension attribute that the script references.
  2. The mbxtype-config file includes the definitions for different user settings that are allowed for the customer (for example, DW for Deskless Worker). 

Worker definitions

  • Deskless Worker mailboxes require MBX=DW.

    • Microsoft Office Outlook Web Access (OWA) is enabled when the following features are turned off:
      • Delegation
      • Inbox Rules
      • IM integration
      • SMS integration (notifications)
    • Microsoft Outlook (MAPI and RPC/HTTPS) is not enabled.
    • ActiveSync is not enabled.
    • Web Services access is not enabled except by LOB applications that use impersonation.
    • IMAP4 is not enabled.
    • POP3 is enabled.
  • Standard mailboxes require MBX=ST.
  • Optional mailboxes require MBX=EX.

For legacy customers 

  • 200 MB Task work mailboxes for legacy clients require MBX=TW.

Several additional scenarios are explained in the following list, together with the expected effect:

  • If the attribute is set to MBX=ST; and then changed to MBX=DW;, the mailbox is changed from standard to deskless worker. 
  • If the attribute is set to MBX=DW; and then changed to MBX=ST;, the mailbox is changed from deskless worker to standard. 
  • If the attribute is not set or is set incorrectly, and then the attribute is updated to a value such as MBX=ST; or MBX=DW;, the mailbox changes when this recognized and supported value is set. 
  • For any mailbox where the value is either missing or invalid, these mailboxes are billed at the customer’s standard mailbox rate.
  • If the attribute is set to MBX=ST; or MBX=DW; and then cleared and set to null, the mailbox remains at the previous size. 
  • MIG=In-progress must be cleared to enable the provisioning script. 
The SetMailboxType process is scheduled to run every 24 hours for customers. It will update the change to the mailbox size and other mailbox properties. These changes are made according to the value set that the customer sets in a predefined Active Directory Domain Services extension attribute. 

By setting this value for each mailbox, customers can take advantage of the Exchange Online SetMailboxType process and larger mailbox sizes. The goal of this process is to give customers more control over their mailbox size limits.

The automated process runs daily on the managed servers, and, if the values that the customers set are recognized by the SetMailboxType script (these values must contain the semicolon (;) character), mailboxes are resized within 24 hours according to these values. If the values are set incorrectly or are left blank for any mailboxes, the SetMailboxType process skips any such mailboxes, and the mailbox remains unchanged.

Follow this link:
Use the SetMailboxType command to modify mailbox size limits

The file size of an Excel workbook may unexpectedly increase exponentially

The file size of a Microsoft Excel workbook may unexpectedly increase exponentially. Additionally, if all the users of a shared workbook save and then close the workbook, the workbook may not decrease in file size as it should.

Note Excel 2007 files are based on a combination of XML and compression, the file types are usually smaller than legacy XLS file types. However, this issue may occur in any of the versions of Excel that are listed in the “Applies to” section.

This issue may occur if Excel closes unexpectedly. In this case, users may not be correctly disconnected from the shared workbook.
To resolve this issue, disconnect all users who are currently not using the workbook, save the workbook, and then close the workbook.

Important Verify with the users whom you want to disconnect that they are no longer actually working on the workbook. If you disconnect an active user, that user’s unsaved work will be lost.

To disconnect users who are currently not using the workbook, follow these steps, as appropriate for the version of Excel that you are running.

Excel 2007

  1. Open the shared workbook in Excel 2007.
  2. Click the Review tab.
  3. In the Changes group, click Share Workbook.
  4. On the Editing tab,
    click the name of each user whom you want to disconnect, and then click Remove User after each name.

Microsoft Office Excel 2003 and earlier versions of Excel

  1. On the Tools menu, click Share Workbook, and then click the Editing tab.
  2. In the Who has this workbook open now box, review the list of users.
  3. Click the name of each user whom you want to disconnect, and then click Remove User.
The issue that is described in this article may occur regardless of whether you use the Don’t keep change history option in Excel. Excel keeps track of any changes that are required to synchronize the workbook between users. Excel stores these changes in memory until you save the workbook. When you save the workbook, Excel saves these changes to the hard disk drive.

Whenever Excel closes unexpectedly, ghost user names can remain in the shared workbook. The workbook tracks the version of a shared workbook to which a user was last synchronized. The workbook does this so that changes that are made after the synchronization are not purged.

To avoid the issue that is described in this article, use the following suggested practices:

  • Save frequently. The longer the interval between save operations, the more memory that is used by stored change records that have not been saved to the file.
  • Make sure that each user closes the shared workbook daily. This procedure helps prevent ghost user names. Additionally, this procedure enables change records that are in memory to be purged.
  • Periodically, look for and remove any ghost user names that are left in the workbook. Then, save and then close the workbook.

Visit site:
The file size of an Excel workbook may unexpectedly increase exponentially

Communicator generates an Outlook integration error

Article ID: 2000886 – Last Review: February 15, 2012 – Revision: 16.0

When you try to sign in to Microsoft Office Communicator 2007, you experience one or more of the following symptoms:

  • Cannot view presence in Outlook.
  • Cannot integrate with Outlook because Outlook mail profile is not configured correctly’ error message.
  • Cannot connect to Exchange Web Services.
  • Unable to pull Free/Busy information.
  • Communicator self-presence not updating per Outlook calendar.
  • Cannot connect to Microsoft Office Outlook to open the desired folder.  Please close any open outlook dialog boxes and try again’ error message. 
  • Unable to save Communicator Conversations to Outlook.

These issues occur when one or more of the following conditions are true:

  1. You are not signed into the Office Communicator client. Communicator Web Access (CWA) does not provide integrated presence in Outlook.
  2. Your Outlook settings are not configured to display presence in Outlook.
  3. Your mail profile is not configured to use the SMTP that matches the SIPURI information that used to sign into Office Communicator.
  4. Microsoft Office or Outlook may have corrupted or outdated DLL files.
  5. The Microsoft Exchange Free/Busy service is unavailable.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756  How to back up and restore the registry in Windows

To resolve these issues, you can use one or more of the following methods depending on the symptoms:

Note: Make sure that you are signed into the Office Communicator client on a computer that is also running Outlook.

Presence issues in Outlook or unable to save Communicator conversations in Outlook

Method 1: Verify or enable “Conversation History” in Communicator

  1. Close Outlook.
  2. In Communicator, click Tools, click Options, click to enable the Save my instant message conversations in the Outlook Conversation History folder check box, and then click OK.
  3. Open Outlook, verify that the Conversation History folder is populated in Outlook. the Conversation History folder is typically located above the Deleted Items folder.

Method 2: Verify that Outlook is configured to display presence

  1. In Outlook 2003, click Tools, click Options, click Contacts, make sure that the Display online status next to name check box is enabled and the Only display status for people in the To and Cc lines when you rest the pointer on the name check box is not enabled.
  2. In Outlook 2007, click Tools, click Options, click Other.
  3. Make sure that the Display online status next to name check box is enabled and the Display online status in the To and Cc fields only when mouse pointer rests on a Person is enabled.

Method 3: Verify the EnableEWSFallback and the DisablePresenceNote Registry Keys 

  1. Close Outlook and Communicator
  2. Open registry editor.
  3. Navigate to HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftCommunicatorEnableEwsFallback=1
  4. Verify the it is set to 1:
    1. If it is not, set it to 1 and proceed to step 5
    2. If it is set, proceed to step 7
  5. Restart Communicator
  6. In Communicator, type a new note, clear the note, and verify that the note field is empty.
  7. Go back into Registry Editor.
  8. Navigate to HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftCommunicatorDisablePresenseNote=1.
  9. Set DisablePresenseNote to 0.
  10. Restart Outlook, and then restart Communicator.

Method 4: Manually adjust the registry keys (*This method may not be possible for some customer because of IT policy restrictions.)

  1. Close Communicator, Outlook, and any other Office applications
  2. Open Registry Editor.
  3. Locate the following registry sub keys:
    1. HKEY_CURRENT_USERSoftwareMicrosoftOffice11.0CommonPersonaMenu.

      • In the right-hand panel Make sure (Default) value is not set, EnableDynamicPresence data is set to 1, QueryServiceForStatus is set to 2, and RTCApplication is set to 3.
    2. HKEY_CURRENT_USERSoftwareMicrosoftOffice12.0CommonPersonaMenu.
      • In the right-hand panel Make sure (Default) value is not set, QueryServiceForStatus is set to 2, and RTCApplication is set to 3.
    3. HKEY_CURRENT_USERSoftwareMicrosoftOffice12.0OutlookIM.
      • In the right-hand panel Make sure (Default) value is not set, EnablePresence data is set to 2, and SetOnlineStatusLevel is set to 3.
  4. Start Communicator.
  5. Start Outlook. 

If the issue(s) persists, create the registry key below.  This registry key provides data that enables logging for the MSO-Communicator presence feature set, showing exactly what was happening when Outlook requested presence information. 

  1. Click Start, and then click Run.
  2. In the Open box, type REGEDIT, and then click OK to start Registry Editor.
  3. Navigate to Key:  HKEY_CURRENT_USERSoftwareIM Providers.
  4. Create the following DWORD value: OfficePresenceLogging with Value: 1.

 The log file is created in the %userprofile%Tracing folder and the filename is OfficePresence-#.log (where # is an integer).

Cannot integrate with Outlook because Outlook mail profile is not configured correctly or Cannot connect to Exchange Web Services

Method 1: Remove and then re-add Microsoft Office Communicator 2007 Add-in for Outlook:

  1. Close Office Communicator
  2. In Outlook, click Tools, click Trust Center, select Add-ins. In the Add-ins dialog box, next to Manage, select COM Add-ins, and then click Go. In the COM Add-ins dialog box, select the Microsoft Office Communicator 2007 Add-in, click Remove, click OK, and then restart Outlook.
  3. In Outlook, click Tools, click Trust Center, click Add-ins. In the Add-ins dialog box, next to Manage, select COM Add-ins, and then click Go. In the COM Add-ins dialog box, click Add… .
  4. Navigate to Program FilesMicrosoft Office Communicatorocoffice.dll.
  5. Click OK, and then quit Outlook.
  6. Restart Communicator.
  7. Restart Outlook. 

Method 2: Repair or rebuild your mail profile:

  1. Close Communicator  and Outlook.
  2. Open the Control Panel, and then double-click MailOn 64-bit operating systems, you must select 32-bit Control Panel, and then select the Mail applet.
  3. Click Show Profiles.
  4. Select the profile, and then click Properties.
  5. Click Email Accounts.
  6. Click the E-mail tab, and then click Repair.
  7. In the E-mail Address field enter your Communicator sign-in address, for example: someone@.com
  8. Click Next.
  9. Click Finish, and then restart Outlook and allow the profile to load.
  10. Close Outlook after profile setup is complete.
  11. Restart Communicator.
  12. Restart Outlook.
  13. If the repair does not resolve the issue, you can try to recreate the mail profile.

Method 3: Recreate the mail profile

  1. Close Communicator & Outlook

  2. Create a new profile:

    1. Open the Control Panel, and then double-click MailOn 64-bit operating systems, you must select 32-bit Control Panel, and then select the Mail applet.
    2. Click Show Profiles.
    3. Select Add, and enter a name for the new profile.

    4. During the Auto Account setup process, change the default e-mail address from its current value to your Communicator sign-in address.

    5. Click Next and the new profile is configured automatically.

  3. Delete old profile

    1. Select old mail profile.

    2. Select Remove.

    3. Click Yes.

    4. Click OK, and then close the Mail applet.

  4. Re-launch Outlook and allow the profile to load.

  5. Close Outlook after the profile setup is complete.

  6. Restart Communicator.

  7. Restart Outlook.

Scenario 1 : ‘The email address that is used in your default Outlook profile differs from the sign-in address that is used in Lync 2010′ error 

Resolution 1:  Verify the user’s primary SMTP address.  To do this, follow these steps:

  1. Verify that the user’s Primary SMTP setting matches the user’s SIP Address setting. 

  2. If you change the Primary SMTP or SIP Address setting, wait 24-48 hours for replication to occur. 

 Resolution 2:  Disable the email check.  To do this, follow these steps.

 Note Outlook integration may not work correctly after you perform these steps.

  1. Click Start , click Run, type regedit, and then press ENTER. 

  2.  Locate, and then right-click the following registry subkey:

  3. Point to New, and then click DWORD Value. 

  4.  Type DisableEmailComparisonCheck as the name of new registry entry, and then press ENTER. 

  5. Double-click DisableEmailComparisonCheck, type 1 in the Value data box, and then click OK. 

  6. Close Registry Editor. 

  7. Restart Lync 2010 and Outlook. 

Scenario 2 : ‘Outlook is not installed or configured correctly.  Repair or reinstall Outlook, and then sign out and sign back in to Lync’ error

  1. Click Start , click Run, type regedit, and then press ENTER. 

  2. Locate and then delete the following registry subkey: 

  3. Locate the following subkey, and then make sure that Microsoft Outlook is set as the default mail client:

  4. Restart the computer.

Cannot connect to Exchange Web Services or unable to view Free/Busy information

Method 7: Validate the Free/Busy information by using the Outlook client

If you are unable to view free/busy in Office Communicator, you must first verify that you can view Free/Busy in Outlook by scheduling a new meeting request with multiple attendees, and then using the Scheduling Assistant to view their Free/Busy information.  

Scenario 1: ‘Lync is in the process of determining the location of Exchange Web Services’ or the ‘Lync cannot connect to the Exchange server. Lync will attempt to retry the connection’ error message

These messages typically occur when you sign in to Microsoft Lync 2010. These messages typically disappear after several minutes. If one of these error messages persists or the error message changes to an Outlook Integration error, follow the steps in the scenario in this article that is most appropriate to the error. One of these errors may also occur when you enter incorrect credentials when you try to connect to your Outlook profile, or if you click Cancel in the credentials dialog box.

How to repair Office and perform a clean installation of Office Communicator

  1. Close Communicator and Outlook.
  2. Click Start, click Control Panel, in Windows XP, click Add/Remove Programs, in Windows Vista, click Programs and Features.
  3. Select Communicator.
  4. Click Remove/Uninstall.
  5. Select Microsoft Office installation.
  6. Click Change.
  7. Follow the prompts to run a repair.
  8. Restart the computer.
  9. Reinstall Office Communicator from an approved site.
  10. Start Communicator.
  11. Start Outlook.
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.


APPLIES TO
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Office Communications Online Dedicated
  • Microsoft Office Communicator 2007
  • Microsoft Office Communicator 2007 R2
  • Microsoft Business Productivity Online Suite Federal
  • Microsoft Lync 2010

Other Resources

Other Support Sites

Community

Get Help Now

More here:
Communicator generates an Outlook integration error

How to contact a Microsoft Product Activation Center by phone

Do you need to call a Microsoft Product Activation Center to activate a Microsoft product?
Do you need to locate the right telephone number to call?

This article describes how to find a phone number for a Microsoft Product Activation Center for the following products:

If the information in this knowledge base article did not help, select one of the following options:

Read More:
How to contact a Microsoft Product Activation Center by phone

User information is not automatically populated in required fields when you add a user to Microsoft Dynamics CRM

Consider the following scenario in Microsoft Dynamics CRM. On the User page, you type a user name in the Domain Logon Name field to add the user to Microsoft Dynamics CRM. Then, you click in another field. In this scenario, the user information is not automatically populated in the required fields as expected. For example, no values are populated in the First Name field or in the Last Name field.

This problem occurs if the following conditions are true:

  • The user whom you want to add to Microsoft Dynamics CRM is from another domain. 
  • A one-way trust is specified for the other domain.
This problem occurs because the one-way trust cannot automatically resolve the user information to Microsoft Dynamics CRM. 
To resolve this problem, manually enter the user information in the required fields. For example, type the first name of the user in the First Name field, and then type the last name of the user in the Last Name field.

View the original here:
User information is not automatically populated in required fields when you add a user to Microsoft Dynamics CRM

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

Recent Comments

    Archives

    Categories