microsoft

Page 1 of 11712345...102030...Last »

Error message when you try and inactivate a customer in SOP

Published January 2, 2013 | By Microsoft Support

When you try to set a customer to inactive in the Customer Maintenance window you receive the following error:

“You cannot inactivate a customer record with unposted or posted transactions.”

This problem/behavior occurs when there are open Sales Order Processing or Receivables Management (not yet in history) transactions still in GP for the customer you are trying to inactivate.

The system will only allow you to successfully mark “Inactivate” for a Customer ID in the Customer Maintenance window if you do not have any unposted transactions and if the posted transactions are in History.

You need to see if there are any OPEN Receivables Management transactions or unposted Sales Order Processing transactions for the customer. To resolve this problem, follow these steps:

1.) Navigate to the Receivables Transaction Inquiry – Customer window. To get to this window go to the Inquiry menu, point to Sales, and then click Transaction by Customer.

2.) Enter the customer ID and mark the “Open” checkbox only. Then click Redisplay.

3.) If there are any RM transactions with an Origin of OPEN, then you will not be able to inactivate this customer until the transactions are moved to history.

4.) To move them to history you will need to run the Paid Transaction Removal routine on this customer. Before running the Paid Transaction Removal routine you will want to make sure you are maintaining history on the customer by looking at the Customer Maintenance Options window. To get to this window go to the Cards menu, point to Sales, click Customer, select your customer, and then click Options.

5.) Make sure the checkboxes in the Maintain History section are marked. If they are unmarked and you run the Paid Transaction Removal routine the transactions for this customer will be removed from the system instead of being moved to history.

6.) Run Paid Transaction Removal by navigating to the Microsoft Dynamics GP menu, point to Tools, point to Routines, point to Sales, and then click Paid Transaction Removal.

7.) In the Paid Transaction Removal routine window, enter the customer ID in the “From” and “To” fields and click Process.

Next we will check to see if there are any un-posted SOP transactions for this customer using these steps:

1.) Navigate to the Sales Order Processing Document Inquiry window. To get to this window go to the Inquiry menu, point to Sales, and then click Sales Documents.

2.) Change the Documents drop down to “by Customer ID” and enter the customer you are trying to inactivate in the From and To fields.

3.) Mark the “Unposted” option and click Redisplay.

4.) If there are any transactions showing they will need to be moved to history or removed from the system before you can inactivate the customer.

5.) To move SOP transactions to history you can use the Reconcile – Remove Sales Documents utility. To get to this window go to the Microsoft Dynamics GP menu, point to Tools, point to Utilities, point to Sales, and then click Reconcile-Remove Sales Documents.

6.) Mark the “Remove Completed Documents” option and enter the transaction in the From and To fields. Click Process.

Note: If you do not have the Maintain History checkboxes marked for this customer in the Customer Maintenance Options window this utility will remove the transaction from the system instead of moving it to history.

After taking care of any unposted transactions and any posted transactions that are not in history, you should be able to inactivate the customer without error.

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: 2743701 – Last Review: January 2, 2013 – Revision: 1.0


Applies to
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Sales Order Processing
kbmbsmigrate kbsurveynew KB2743701

View the original here:
Error message when you try and inactivate a customer in SOP

Posted in KB Articles | Tagged , , , , , , , , , , ,

Support with Microsoft Dynamics CRM 2011 and Microsoft Office 2013

Published October 24, 2012 | By Microsoft Support

Microsoft Dynamics CRM 2011 with Update Rollup 10 and up is compatible with Microsoft Office 2013 for the scenarios described below. This article describes the functional differences between Update Rollup 10 and Update Rollup 11. 

What is compatible with Update Rollup 10?

· Office 2013 MSI – Basic functional compatibility (some known issues*).  

· Office 2013 Click to Run (C2R) (standalone) – Preview of upcoming functional compatibility (some known issues*).

· Office 2013 C2R (side by side w/ Office 2010 only) – Use on Test environments only. When your organization is migrated to Office 2013, it will become the default version of Office. Because of this, your Office 2010 CRM instance is not guaranteed to be fully functional. A list of the main known issues are identified below**.

· Windows 8 – Functional compatibility (w/ manual WIF enablement)

What is compatible with Update Rollup 11?

· Office 2013 MSI – Enhanced compatibility (functional known issues fixed).

· Office 2013 Click to Run (C2R) (standalone) – Functional compatibility at parity with MSI

· Office 2013 C2R (side by side w/ Office 2010 only) – Preview of upcoming side by side support with Office 2013 for Office 2010. Client will only work on Office 2013 and will be blocked in Office 2010

· Windows 8 – Enhanced compatibility, WIF is automatically enabled in Outlook Client setup.

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: 2744957 – Last Review: October 24, 2012 – Revision: 5.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB2744957

Originally posted here:
Support with Microsoft Dynamics CRM 2011 and Microsoft Office 2013

Posted in KB Articles | Tagged , , , , , , , , ,

Message when you try to open an attachment in Outlook Web Access or Outlook Web App: "Right-click the link, and then click ‘Save Target As’ to save the attachment."

Published March 15, 2012 | By Microsoft Support

Consider the following scenarios.

Scenario 1

  • A user’s mailbox is hosted on a server that is running Microsoft Exchange Server 2007.
  • The user starts Microsoft Office Outlook Web Access.
  • Either of the following conditions occurs:
    • The user views a signed or encrypted email message.
    • The user composes a new email message in Windows Internet Explorer 8 or a later version.

  • The user tries to view an email attachment.

Scenario 2

  • A user’s mailbox is hosted on a server that is running Microsoft Exchange Server 2010.
  • The user starts Microsoft Outlook Web App.
  • Either of the following conditions occurs:
    • The user views a signed or encrypted message.
    • The user composes a new email message.
  • The user tries to open an email attachment.

In either of these scenarios, the user cannot view the attachment, and the user receives a message that resembles the following:

Right-click the link, and then click ‘Save Target As’ to save the attachment.

This issue occurs if the S/MIME control is installed.
This behavior is by design.
The behavior that is mentioned in the “Symptoms” section is intended to increase compatibility between browser versions. Modern browsers, and this includes Windows Internet Explorer 8 and later versions, help provide increased stability by starting a new process to host the document for a new window.

However, earlier versions of the S/MIME control did not expect a new process to be created. Therefore, newer versions of the S/MIME control force the attachment to be saved in order to increase compatibility.

For more information about opening files that are attached to email messages, visit the following Microsoft TechNet website: For more information about opening files in Microsoft Outlook Web App, visit the following Microsoft TechNet website:

Visit site:
Message when you try to open an attachment in Outlook Web Access or Outlook Web App: "Right-click the link, and then click ‘Save Target As’ to save the attachment."

Posted in KB Articles | Tagged , , , , , , ,

You cannot set the "Country/region" attribute of a user mailbox to "Curaçao," "Bonaire, Sint Eustatius and Saba," or "Sint Maarten (Dutch part)" by using the Exchange Management Console on an Exchange Server 2007 server

Published March 14, 2012 | By Microsoft Support

On a Microsoft Exchange Server 2007 server that is running Windows Server 2008 or Windows Server 2008 R2 and has hotfix 2604521 installed, one of the following scenarios occurs.
Scenario 1

You try to use Exchange Management Console to set the Country/region attribute of a user mailbox to one of the following three countries or regions:

  • Curaçao
  • Bonaire, Sint Eustatius and Saba
  • Sint Maarten (Dutch part)

In this situation, the country options are not displayed.

Scenario 2

 Consider the following scenario:

  • You have hotfix 2607863 installed on the Exchange Server 2007 server.
  • You use the Active Directory Users and Computers MMC snap-in to set the Country/region attribute of a user account to one of the following three countries or regions:
    • Curaçao
    • Bonaire, Sint Eustatius and Saba
    • Sint Maarten (Dutch part)
  • You try to use Exchange Management Console to view the Country/region attribute of the user mailbox.

In this scenario, you receive the following error message:

The properties on %useraccount% have invalid data. If you click ‘OK’, default values will be used instead and will be saved if you do not change them before hitting ‘Apply’ or ‘OK’ on the property page. If you click ‘Cancel’ the object will be displayed read-only and corrupted values will be retained. The following values have invalid data: CountryOrRegion

This issue occurs because Exchange Server 2007 does not handle the new countries or regions correctly.
To resolve this issue, install the following update rollup:

2608656 

(http://support.microsoft.com/kb/2608656/
)
Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:  
2604521 

(http://support.microsoft.com/kb/2604521/
)
 You cannot set the “Country/region” attribute of a user account to “Curaçao,” “Bonaire, Sint Eustatius and Saba,” or “Sint Maarten (Dutch part)” in Windows Vista or in Windows Server 2008
2607863 

(http://support.microsoft.com/kb/2607863/
)
 You cannot set the “Country/region” attribute of a user account to “Curaçao,” “Bonaire, Sint Eustatius and Saba,” or “Sint Maarten (Dutch part)” in Windows Vista or in Windows Server 2008

Read the article:
You cannot set the "Country/region" attribute of a user mailbox to "Curaçao," "Bonaire, Sint Eustatius and Saba," or "Sint Maarten (Dutch part)" by using the Exchange Management Console on an Exchange Server 2007 server

Posted in KB Articles | Tagged , , , , , , , , , , ,

Week numbers do not match between OWA and Outlook calendars in the English and French versions in an Exchange Server 2007 environment

Published March 2, 2012 | By Microsoft Support

In a Microsoft Exchange Server 2007 environment, the week numbers that are displayed in the Outlook Web Access (OWA) calendar do not match the week numbers that are displayed in the Microsoft Office Outlook calendar. This issue occurs when you use the English or French version of OWA and of Outlook. For example, in the English version of OWA, the first week number is 2 instead of 1 for the year 2010. However, it is different when you use the English version of Outlook.
To resolve this issue, install the following update rollup:
2608656 

(http://support.microsoft.com/kb/2407025/
)
 Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3

After you install this update rollup, Exchange Server 2007 OWA provides an option to select when the week numbers start.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about the client features in Exchange Server 2007 OWA, visit the following Microsoft website:For more information about how to display the week numbers in Outlook, visit the following Microsoft website:

Original post:
Week numbers do not match between OWA and Outlook calendars in the English and French versions in an Exchange Server 2007 environment

Posted in KB Articles | Tagged , , , , , , ,

An Exchange Server 2007 Transport Rule does not work as expected

Published March 1, 2012 | By Microsoft Support

A Microsoft Exchange Server 2007 Transport Rule does not work as expected. For example, an email message that an administrator expects to be rejected may instead be delivered.
This issue can occur if the Transport Rule is based on a regular expression. For example, this issue can occur if you use the “$” character to create a pattern-matching regular expression.

Note Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010 do not implement the full Microsoft .NET Framework regular expression classes. Additionally, the intermediate language that is generated may be incorrect.

To work around this issue, use one of the following methods.

Method 1

Create a Transport Agent and then implement your own .NET Framework regular expressions to route email messages.

Method 2

Use a filter to automatically process email messages. For example, use Microsoft ForeFront Security for Exchange Server to filter email messages based on the email originator and email recipient.

Regular expressions are a powerful, flexible way to evaluate a character sequence for matching against a given series of characters. Typically, a regular expression is written in a programming language such as C++ or C#. The regular expression can then be interpreted by a regular expression processor. The processor examines the character sequence and identifies parts that match the provided characters.

You can create a Transport Rule based on regular expressions in the Exchange Management Shell (EMS) by using the New-TransportRule cmdlet. When you use the Conditions parameter, the Exchange regular expression implementation is used. You can use regular expressions in any predicate that accepts the “Patterns” predicate property.

Transport Rule conditions and exceptions consist of one or more predicates. Predicates instruct the Transport Rules agent on a Hub Transport server (or the Edge Rules agent on an Edge Transport server) to examine a specific part of an email message. Those specific parts include sender, recipients, subject, other message headers, and message body. Then, the Transport Rule determines whether the rule should be applied to that message. Therefore, predicates act as building blocks for conditions and exceptions.

In the Exchange Management Console, you can use regular expressions with any condition or exception that contains the words “text patterns.” For example, you can use regular expressions with the following condition:

“when the From address contains text patterns”

Note The “Patterns” predicate accepts a regular expression that can be used to match text that follows an identifiable pattern. You must enclose the expression in quotation marks (“).

For more information about Transport Agents in Exchange Server 2010, visit the following TechNet website:
For information about how to use the NewTransportRule cmdlet, visit the following TechNet website:
For information about regular expressions and how to use regular expressions in Exchange Server 2007 Transport Rules, visit the following TechNet website:
For information about how to use predicates to create conditions and exceptions in an Exchange Server 2010 Transport Rule, visit the following TechNet website:

Continue Reading:
An Exchange Server 2007 Transport Rule does not work as expected

Posted in KB Articles | Tagged , , , , , , , , ,

Microsoft Fix it Center Pro automated diagnostic portal

Published February 28, 2012 | By Microsoft Support

Fix it Center Pro
(https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase)
 (beta) is an automated troubleshooting service from Microsoft. This service can help make it easier to identify solutions to problems with Microsoft applications.

Fix it Center Pro can use targeted analysis to scan your system to identify and resolve specific problem areas. In addition, Fix it Center Pro can help find the most suitable content, tools, and forums and help address the symptom that you see. Fix it Center Pro can also help with a troubleshooting task that you are performing through its Guided Search feature.

Fix it Center Pro has several features that can be used to help diagnose issues. Those features are as follows:

Guided Search helps you find the most suitable content, tools, and forums and helps address the symptom that you see or the troubleshooting task that you are performing.

Work Items enables you to track your research as you are resolving an issue. If you cannot solve a technical issue on your own, click the Escalate button to turn your work into a Support Request (in which case, charges may apply).

Support Requests enables you to track or create new Support Requests with Microsoft (in which case, charges may apply).

Analysis sessions scan your system to identify solutions for specific problem areas. The results are uploaded to Microsoft servers to be processed and to identify any known issues. If a known issue is found, a message is displayed that explains the steps that you can take to resolve the problem. You may escalate the diagnostic results into a Support Request for more help from Microsoft if you want (in which case, charges may apply).

Work Items, Analysis, and Support Requests can all link to one another so that the relationships between them are clear and easy to track.

Diagnostic results

  • If the diagnostic does not resolve your issue, you can easily create a Support Request. To do this, click the New button in the Support Request Toolbar. Or, click the Escalate button in a Work Item (in which case, charges may apply).
  • If you chose to open a Support Request, and the Fix it Center Pro diagnostic resolves your issue before you start to work with a Microsoft Support Professional, you will not be charged for the Support Request.

How to return to Fix it Center Pro

Diagnostic results are usually displayed immediately after the troubleshooter completes its scan. However, there are some instances where it can take up to an hour for deep analytics to be completed. Your computer will not be affected by these deep analytics because the analysis is processed in Fix it Center Pro. You can leave Fix it Center Pro and return to the site later to review the diagnostic results.

To return to Fix it Center Pro, follow these steps:

  1. To return to Fix it Center Pro, click the following link:
  2. If you are prompted, sign in by using your Windows Live ID.
  3. To view your Analysis Package, in the left-side navigation area, click Analysis, and then locate the name that you entered earlier.
  4. To view your Support Requests with Microsoft, in the left-side navigation area, click Support Requests.

See original article:
Microsoft Fix it Center Pro automated diagnostic portal

Posted in KB Articles | Tagged , , , , , , , , , ,

How to troubleshoot Exchange Server 2007 and Exchange Server 2010

Published February 25, 2012 | By Microsoft Support

The “Exchange Server 2007 SP3 and Exchange Server 2010 Troubleshooter for Windows 2008 R2″ tool collects a comprehensive set of information for troubleshooting Exchange Server 2007 SP3 and Exchange Server 2010 issues in Windows Server 2008 R2. This troubleshooter is integrated with the Microsoft Fix it Center Pro service. This service can perform automated diagnostic analysis to identify solutions.

To run this troubleshooter, follow these steps:

  1. Visit the Microsoft Fix it Center Pro
    (https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase/Create?showReturn=True)
     portal.
  2. If you are prompted, sign in by using your Windows Live ID.
  3. In the Analysis packages list, click Exchange Server 2007 SP3 and Exchange Server 2010 Troubleshooter for Windows 2008 R2.
  4. In the Create Analysis Session window, type a descriptive name for the session, and then click Save.

    Note You will use the name that you enter to view the analysis results later.

  5. Follow the instructions to download and run the analysis package.
  6. To view the analysis results, open the Fix it Center Pro – Analysis
    (https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase?shcID=SHC5007487727638252&maximizeDetails=False)
     webpage.
  7. Click the Analysis Session name that you created in step 4 to view possible solutions.
For more information about Fix it Center Pro, please see:For more information about this troubleshooter and what it scans, please see the following Microsoft Knowledge Base article:

See the article here:
How to troubleshoot Exchange Server 2007 and Exchange Server 2010

Posted in KB Articles | Tagged , , , , , , , , , , ,

Outlook connects to an old Exchange server after you move a mailbox from an Exchange Server 2007 server to an Exchange Server 2010 server

Published November 29, 2011 | By Microsoft Support

Assume that you move a user’s mailbox from an Exchange Server 2007 server to an Exchange Server 2010 server, or you move a user’s mailbox from an Exchange Server 2010 server to another Exchange Server 2010 server. After the mailbox is moved, the user receives the following error message when the user opens Outlook:

Microsoft Exchange administrator has made a change that requires you to quit and restart Outlook.

Additionally, the user also encounters the following symptoms:

  • After the user restarts Outlook, Outlook continues to connect to the old server.
  • If the user runs a repair on the profile, the same error message is received.

Notes

  • If you use the Test-EmailAutoConfig cmdlet and specify the user’s mailbox, the correct information of the mailbox configuration is returned.
  • If Outlook is running, this issue is recovers by itself in 30 minutes or more.
  • The error message does not occur after the user manually updates the profile with the new mailbox server, or creates a new Outlook profile.
  • This issue occurs in Exchange Server 2010 Release to Manufacturing (RTM) and Exchange Server 2007 earlier than Service Pack 3 (SP3).

To resolve this issue, install Exchange Server 2007 SP3 on the Exchange Server 2007 mailbox server and install Exchange Server 2010 SP1 on the Exchange Server 2010 mailbox server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
After a Move-Mailbox operation, Outlook receives a referral from the Exchange mailbox server where the mailbox was formerly located. In this referral response, an ecWrongServer value is returned to Outlook. The response includes the homeMDB attribute that points to the new Exchange mailbox server for the user’s mailbox. Before you install Exchange Server 2007 on the Exchange Server 2007 mailbox server and Exchange Server 2010 SP1 on the Exchange Server 2010 mailbox server, the behavior of the old Exchange mailbox server is as follows:
  • The old Exchange server sends its own name as the new homeMDB server in the ecWrongServer response name. Therefore, Outlook continues to connect to the old Exchange server.
  • The old Exchange server provides a referral to the new Exchange server. But the profile still shows the Exchange server as the old Exchange server.
  • When you view the General tab in the Connection Status, there is a referral to the new Exchange server.

Delay in updating the Profile

If Outlook is running, this issue eventually resolves by itself in 30 minute or more. This is especially true if the user has many connections to other servers, such as shared folders or shared mailboxes and Calendars. This is an indicator that Mailbox Cache Age Limit is set to a value that is too high.

This issue can be corrected by reducing the cache expiration time, for more information, visit the following Microsoft website:

To change the Mailbox Cache Age Limit value, follow these steps:

  1. On the Exchange Server Mailbox servers, click Start

    Collapse this imageExpand this image

    , type regedit in the Start Search box, and then press ENTER.

  2. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeISParametersSystem

  3. Right-click ParametersSystem, click New, and then click DWORD (32-bit) Value.
  4. Type Mailbox Cache Age Limit, and then press ENTER.
  5. Right-click Mailbox Cache Age Limit, and then click Modify.
  6. In the Base tab, select Decimal.
  7. In the Value data box, type a positive integer to specify the Mailbox Cache Age Limit in minutes. The default value is 2 hours (120 minutes).

Time to update profile

After you reduce the Cache limit to a value such as 15 minutes, you may still experience delays in updating the profile.

The reason for this delay is that the Exchange server cache array on the client is currently limited to 16 entries at a time. Each entry expires in 60 seconds. The client behavior is to verify an entry that is close to expiration and replace it with the newest requested server. If there are many connections at the startup of the Outlook client, the new home server may not be inserted into the array for several minutes. A minute or more delay in updating the Outlook profile is common.

Note If the old Exchange server is turned off before you restart Outlook, clients cannot connect to the new homeMDB server  if the profile is not updated.

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

978469 

(http://support.microsoft.com/kb/978469/
)
 A mailbox that was moved from an Exchange Server 2007 server to an Exchange Server 2010 server cannot be accessed by using Outlook

For more information about how to obtain the latest Service Pack or Update Rollup for Exchange Server 2007, visit the following Microsoft website:
For more information about Exchange Server 2010 Servicing, visit the following Microsoft website:

Follow this link:
Outlook connects to an old Exchange server after you move a mailbox from an Exchange Server 2007 server to an Exchange Server 2010 server

Posted in KB Articles | Tagged , , , , , , , , , , ,

A client does not display email message content in an Exchange Server 2007 SP3 RU1 environment

Published October 31, 2011 | By Microsoft Support

Consider the following scenario:
  • You apply Update Rollup 1 (RU1) for Microsoft Exchange Server 2007 Service Pack 3 (SP3).
  • By default, the Best body format option is set for POP3 and IMAP4 message retrieval on a Client Access server.
  • The POP3 or IMAP4 client cannot display the HTML message format, and retrieves email messages from Exchange Server 2007 server.

In this scenario, the POP3 or IMAP4 client does not display the message content.

This issue occurs because the POP3 or IMAP4 clients that use the Best body format option only retrieve the native content that is stored on the Exchange Mailbox server. This behavior causes the POP3 or IMAP4 clients to no longer receive an additional text-only copy of the message. Therefore, if a client is unable to display the HTML message format, the content of the email message cannot be displayed.
To work around this issue, configure the message retrieval settings for HTML and alternative text. This configuration is set for the POP3 and IMAP4 services on each Client Access server that provides service to users. Additionally, the setting change takes effect after the affected services are restarted.
For more information about how to manage POP3 and IMAP4 message retrieval format options, visit the following Microsoft website:For more information about how to manage POP3 and IMAP4, visit the following Microsoft website:For more information about the Set-POPSettings cmdlet, visit the following Microsoft website:For more information about a content retrieval change in Exchange Server 2007 SP3 Update Rollup 1, visit the following Microsoft website:

Read More:
A client does not display email message content in an Exchange Server 2007 SP3 RU1 environment

Posted in KB Articles | Tagged , , , , , , , , , ,
Page 1 of 11712345...102030...Last »

Recent Comments

    Archives

    Categories

    Microsoft Knowledge Base Wiki

    Copyright © 2013. All Rights Reserved.

    Designed by Sivakumar Venkataraman.