Microsoft Knowledge Base Wiki

When you try to use the ledger transaction functions in Microsoft Business Solutions – Axapta 3.0, you may receive the following error message:

Therefore, the ledger settlement cannot select the records.

This problem occurs if the value in the RecId field is longer than 10 digits and contains a minus sign (-).
The problem occurs because the LedgerTrans.RecId value is truncated. For example, a value of “-2147334980″ is truncated to “-214733498″. The LedgerTrans table and LedgerTransSettlement table are related through the LedgerTrans.RecId value. Therefore, when the LedgerTrans.RecId value is truncated, the relationship breaks.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Axapta 3.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft Business Solutions – Axapta 3.0 that contains this hotfix.

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

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.
If you are a customer and if you do not have a Premier Support Agreement with Microsoft, you must contact your partner to obtain this hotfix.

Installation information

If you have customizations to one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

1. Review the changes that are documented in the .xpo file.
2. Apply these changes in a test environment before you apply the hotfix in a production environment.

For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

Prerequisites

You must have Service Pack 2 for Microsoft Business Solutions – Axapta to install this hotfix.

Removal information

You cannot remove this hotfix.

Restart requirement

If you are prompted to restart your computer, you must restart your computer after you apply this hotfix.

Objects that are affected

This hotfix affects the following objects:

• Form:LedgerTransSettlement

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
This problem was first corrected in Microsoft Axapta 3.0 Service Pack 3.

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

When you create an all-day activity in Microsoft Dynamics CRM, the due date for the activity is displayed as the day after the end date of the activity. This due date is displayed in the associated activities view.

This behavior occurs if you select the All Day Event check box in the Appointment dialog box. However, you do not set the start time, and you do not set the end time.

To work around this behavior, clear the All Day Event check box in the Appointment dialog box. Then, set the start time, and set the end time.

Steps to reproduce the behavior

1. Create a new service appointment. To do this, follow these steps:
   1. Click Service, point to New Activity on the New menu, and then click Appointment.
   2. In the Appointment dialog box, click the Details tab.
   3. In the Regarding list, click an account.
   4. On the Appointment tab, set the start date, and set the end date. Then, select the All Day Event check box.
   5. Click Save and Close.
2. Click Service, click Accounts, and then double-click the account that you clicked in step 1c.
3. Click Activities, and then click the service appointment that you created in step 1.

   Note The Due Date field displays the day after the end date that you set in step 1d.

In the associated activities view, the Due Date field displays MM/DD/YYYY 12:00:00AM. In this situation, this is the beginning of the day after the end date of the activity.

This behavior is by design.

Article ID: 935252 – Last Review: May 21, 2013 – Revision: 2.0

Assume that you install Microsoft Exchange 2010 Service Pack 3 (SP3) in an Exchange Server environment. There are many Outlook Anywhere (RPC over HTTP) clients in the environment. When the Outlook Anywhere clients try to connect to the Exchange server, the Outlook Anywhere clients are not connected. Additionally, the Outlook Anywhere clients receive the following error message:

This issue occurs because the limit of RPC over HTTP requests that ASP.NET can process is reached. 

The RPC over HTTP requests in Exchange Server 2010 SP3 rely on the ASP.NET runtime to process the requests. However, the default limit of ASP.NET requests is 25,000. 

Note In versions of Exchange Server earlier than Exchange Server 2010 SP3, RPC over HTTP requests do not rely on the ASP.NET runtime, and they are not affected by the request limit.

To resolve this issue, increase the limit of ASP.NET requests to a number that is appropriate for the environment. To increase the limit of ASP.NET requests, follow these steps:

1. On the computer that is running the Client Access server role, locate the following file:

   C:WINDOWSMicrosoft.NETFramework64v2.0.50727CONFIGMachine.config

2. Open the Machine.config file.
3. In the section, locate the following line:
4. Change the value of requestQueueLimit property to 65535.

You can use the following counters to monitor the number of ASP.NET requests and RPC over HTTP connections:

• ASP.NET Apps v2.0.50727_LM_W3SVC_x_ROOT_RPCRequests Executing
• RPC/HTTP ProxyCurrent Number of Incoming RPC over HTTP Connections

When the issue occurs, the following errors are logged in the Internet Information Server (IIS) log:

Article ID: 2832198 – Last Review: May 21, 2013 – Revision: 5.0

The following error may occur when the Maximum Worker Processes have been modified from the default value of 1 in Microsoft Dynamics CRM:

“Error: The Sandbox SDK Listener failed to start” – When attempt to navigate a recently imported Customization (with plugins) to a Dynamics CRM organization, it throws a following error:-

The Sandbox SDK Listener failed to start.
Source: w3wp.exe (3504)
Endpoint: net.tcp://localhost/CrmSandboxSdkListener-w3wp
Error: System.ServiceModel.AddressAlreadyInUseException: The TransportManager failed to listen on the supplied URI using the NetTcpPortSharing service: the URI is already registered with the service.

Modifying the IIS Maximum Worker Processes, otherwise known as Web Gardening, within the Microsoft Dynamics CRM Application Pool is not supported.

In IIS, right-click on Application Pool, select Advance Settings, and in the Process Model section, you will have “Maximum Worker Processes”. Edit the value to “1″.

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: 2833575 – Last Review: May 20, 2013 – Revision: 2.0

Microsoft Forefront Client Security, Forefront Endpoint Protection 2010 and Microsoft System Center 2012 Endpoint Protection scan the files and folders on your computer for malicious programs that are known as malware. By default, all files and folders are included when the programs scan your computer. However, you can configure Forefront Client Security, Forefront Endpoint Protection 2010 and System Center 2012 Endpoint Protection to skip certain files or folders when it scans the computer. It is best not to perform a malware scan on the files for certain programs or for operating system roles. This is to help prevent the following issues: 

• An anti-malware program could incorrectly determine that a program file is malware. This is known as a false positive.
• The anti-malware scan operation could decrease performance for a particular program when that program tries to access its program files.

This article contains links to articles and to Web sites that identify files and folders for certain Microsoft products. We recommend that you exclude these files and folders from Forefront Security and System Center 2012 Endpoint Protection scan operations. 

Note The information in this article also applies to other antivirus or anti-malware programs that you may use. Also, if you run an antivirus or anti-malware program on a computer that is running a third-party program or service, we recommend that you contact the program vendor. The program vendor can help determine whether certain files or folders should be excluded from antivirus or anti-malware scan operations.

The following sections contain information about the files and folders that we recommend be excluded from scanning by anti-malware programs. The information is categorized by the operating system role or by program name. 

Both Forefront Endpoint Protection and System Center Endpoint Protection have preconfigured policy templates for the different server roles. For more information regarding these templates please see http://technet.microsoft.com/en-us/library/gg412475.aspx.

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

Domain controllers

For more information, visit the following Microsoft Web sites:

Microsoft Exchange Server

For more information, visit the following Microsoft Web site:

Forefront Endpoint Protection

For more information, visit the following Microsoft Web site:

Internet Information Server (IIS)

Microsoft Internet Security and Acceleration (ISA) Server

For more information, visit the following Microsoft Web site:

Microsoft SharePoint Portal Server

Microsoft SQL Server

Microsoft Systems Management Server (SMS)

Microsoft Virtual Server 2005 or Microsoft Virtual PC 2004

Windows operating systems

General information

For more information about Forefront Client Security policy-based exclusions, visit the following Microsoft Web site:For more information about how to use Forefront Client Security, see the Forefront Client Security product documentation. This documentation contains the following guides:

• Microsoft Forefront Client Security Getting Started Guide
• Microsoft Forefront Client Security Planning and Architecture Guide
• Microsoft Forefront Client Security Deployment Guide
• Microsoft Forefront Client Security Administrator’s Guide
• Microsoft Forefront Client Security Performance and Scalability Guide
• Microsoft Forefront Client Security Disaster Recovery Guide
• Microsoft Forefront Client Security Security Guide
• Microsoft Forefront Client Security Troubleshooting Guide
• Microsoft Forefront Client Security Technical Reference Guide

To obtain this documentation, visit the following Microsoft Web site:

Article ID: 943556 – Last Review: May 20, 2013 – Revision: 3.1

Consider the following scenario. An Office 365 user uses Windows Internet Explorer 8 to connect to Outlook Web App to access email messages or to sign in to a Secure Sockets Layer (SSL) website that requires authentication. When the user opens a new tab or a new window in the website, the user is prompted to reauthenticate.

This issue occurs when Internet Explorer 8 creates a new process for a new tab or a new window. In this case, the SSL session state of the new tab or of the new window isn’t shared, and an additional authentication dialog box appears.

To fix this issue, install the hotfix that’s referenced in the following Microsoft Knowledge Base article:

Prerequisites

To apply this hotfix, you must have Internet Explorer 8 installed on a computer that’s running one of the following operating systems:

• Windows Vista Service Pack 1
• Windows Server 2008
• Windows 7
• Windows Server 2008 R2

Article ID: 2486120 – Last Review: May 17, 2013 – Revision: 8.0

This article describes how to troubleshoot the following Offline Address Book issues in Microsoft Outlook in a Microsoft Office 365 environment:

• Users can’t download the Offline Address Book.
• Synchronization errors occur in the Offline Address Book.
• You receive nondelivery report (NDR) messages when you use the Offline Address Book to send email messages to users.

To troubleshoot these issues, follow these steps. After you follow each step, test to see whether the Offline Address Book issue is resolved. If the issue is resolved, you don’t have to continue to the next step. If the issue isn’t resolved, go to the next step.

Step 1: Make sure that the global address list (GAL) is up to date

Check whether the GAL is up to date. To do this, make sure that you can view any changes in the GAL by using Microsoft Outlook Web App. If the expected changes aren’t present in the GAL, the changes will not be replicated to the Offline Address Book.

Note If you change your on-premises Active Directory schema and the Windows Azure Active Directory Sync Tool still doesn’t synchronize these changes correctly, go to the following Microsoft website for more info about how to troubleshoot this issue:

If the Online Address Book is correct but the Offline Address Book is still incorrect, go to the next step.

Step 2: Manually download the Offline Address Book and then make sure that Cached Exchange Mode is enabled

Manually download the Offline Address Book in Outlook. This may also resolve nondelivery report issues if you’re using an outdated version of the Offline Address Book. For more information about how to manually download the latest copy of the Offline Address Book, click the following article number to view the article in the Microsoft Knowledge Base:

Then, make sure that Outlook is set up to use Cached Exchange Mode. To do this follow these steps:

1. Take one of the following actions:
   • If you’re running Outlook 2007, click Tools, and then click Account Settings.
   • If you’re running Outlook 2010, click File on the Office ribbon, click Account Settings, and then click Account Settings.
2. In the E-mail Settings dialog box, select the Microsoft Exchange account that you want, and then click Change.
3. In the Microsoft Exchange Settings dialog box, make sure that the Use Cached Exchange Mode check box is selected.

Step 3: Check that the Background Intelligence Transfer Service (BITS) service is running

Check that BITS is started on the computer. Outlook uses BITS to connect to the URL that is provided by the Autodiscover service. To determine whether BITS is started, follow these steps:

1. Click Start, click Control Panel, click Administrative Tools, and then click Services.
2. In the list of services, click Background Intelligence Transfer Service, and then make sure that the status of this service is set to Started.
3. If BITS can’t be started, reinstall it. For more information about how to install BITS, click the following article number to view the article in the Microsoft Knowledge Base:
   968929

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

   Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)

Step 4: Install the latest updates for Office and for Office 365 Desktop

1. Make sure that the latest Microsoft Office service pack is installed.

   Note If you’re using Microsoft Office Outlook 2007, you must, at a minimum, have the 2007 Microsoft Office system Service Pack 1 installed on the computer.

2. Make sure that the latest version of Office 365 Desktop Setup is installed. To install the latest version of Office 365 Desktop Setup, go to the following Microsoft website:

Step 5: Re-create the Outlook profile

If the existing Outlook profile is corrupted, this corruption could be the cause of the issue. Corruption may have occurred if Outlook stopped responding. For more information about how to create and to set up an email profile in Outlook, see the E-mail Setup Help Wizard at the following Microsoft website:

Step 6: Determine whether the Autodiscover service is working, and check access to the Offline Address Book

Note If the Offline Address Book issue wasn’t resolved by using steps 1 through 5, follow this step for validation before you call Support.

Check whether Outlook and the computer can access the Offline Address Book file on the server. This action is typically done by Outlook in the background or when you force a download of the Offline Address Book in Outlook. To do this check, sign in to the Office 365 portal, and then follow these steps:

1. Start Outlook.
2. Hold down the CTRL key, right-click the Outlook icon in the notification area on the right side of the taskbar, and then click Test E-mail AutoConfiguration.
3. Click to clear the Use Guessmart check box, and then click to clear the Secure Guessmart Authentication check box.
4. Click to select the Use AutoDiscover check box.
5. Type the email address and password, and then click Test.
6. On the Results tab, note the path of OAB URL.
7. Click the XML tab, locate the and tags, and then copy the path that is displayed between the tags. Paste the path into the address box in Windows Internet Explorer, add /OAB.xml to the end of the path, and then press Enter.

   The following is an example of what the URL may resemble:

   https://autodiscover.contoso.com/OAB/93179f28-4b4d-4e58-aec1-07bb493be4f4/OAB.xml

8. Note the information that is displayed in the webpage in Internet Explorer. The webpage should contain lots of XML data. The following is an example of the information that should be displayed in Internet Explorer:

   Collapse this imageExpand this image

Article ID: 2429946 – Last Review: May 17, 2013 – Revision: 40.0

Purchase Orders are missing from Analysis Cubes for Dynamics GP.

This is caused by a bug in the PurchaseOrderDetail SSIS package that runs during the data load from Dynamics GP to the Analysis Cubes Data Warehouse database. The bug occurs due to a timestamp comparison on the LastUpdated timestamp and LSTEDTDT/CREATDDT/DOCDATE of the Purchase Order detail line in the Dynamics GP database. The timestamp in the LastUpdated value includes HH:MM:SS whereas the LSTEDTDT/CREATDDT/DOCDATE does not. This difference can cause Purchase Orders to not be included in Analysis Cubes.

Please use the following steps to resolve this issue:

1. Open SQL Server Business Intelligence Development Studio (BIDS).
2. Click File, point to New, and then select Project….
3. Click OK.
4. Right-click SSIS Packages folder in the Solution Explorer pane and then select Add Existing Package.
5. Choose SSIS Package Store for the Package Location.
6. Type in the SQL server name where the Analysis Cubes SSIS packages reside into the Server field.
7. Choose the Authentication type and type in a user if required.
8. Click the ellipses button next to the Package path field.
9. Expand MSDB.
10. Expand your Analysis Cubes SSIS folder.
11. Locate the SSIS package that ends with “PurchaseOrderDetail”. Select it and then click OK.
12. Click OK.
13. Double-click the PurchaseOrderDetail SSIS package in the Solution Explorer pane.
14. Double-click the icon inside the Copy Data from Results to PendingPurchaseOrders Task to open that task.
15. Double-click the icon inside the OLE DB Source entity.
16. Copy the contents of the SQL command text section into a text editor, such as Notepad.
17. In the text editor, use the Replace function to replace ”select @lastdate = DateUpdated from DynamicsGPWarehouse.dbo.LastUpdated where CompanyID = @CompID and TableName = ‘PurchaseOrderDetail’” with “select @lastdate = convert(char(12),DateUpdated,101) from DynamicsGPWarehouse.dbo.LastUpdated where CompanyID = @CompID and TableName = ‘PurchaseOrderDetail’”
18. Go back to BIDS and select all of the text inside the SQL command text section and then press the Delete key to remove the text.
19. Copy the updated text from the text editor into the SQL command text section.
20. Click the Parse Query button. If the query was not parsed successfully, the text was not updated correctly or copied back correctly. Click Cancel on the OLE DB Source Editor window and retry steps 15-20.

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

You have a hybrid deployment of on-premises Microsoft Exchange Server and Microsoft Exchange Online in Microsoft Office 365 in which the following conditions are true:

• The on-premises environment consists of both Exchange 2010 and Exchange 2003 servers.
• The Exchange 2003 public folder is set up to use a custom list instead of routing groups for public folder referrals.

In this scenario, on-premises users who have a mailbox on Exchange 2003 or who are using Outlook 2003 can’t view free/busy information of Office 365 users. However, they can view free/busy information of other on-premises users. Additionally, on-premises users who have a mailbox on Exchange 2010 can view free/busy information of Office 365 users.

This issue occurs if the Exchange 2003 server is unable to refer Outlook to the Exchange 2010 public folder server that contains the replica. Although an Exchange 2010 server is specified in the custom list for public folder referrals, the cost calculation fails. When the Exchange 2010 server is selected in the public folder referral custom list from the Exchange 2003 Management System, the public folder database is displayed instead of the server.

Exchange 2003 incorrectly resolves the Exchange 2010 server in the list of public folder referrals to the GUID of the Exchange 2010 public folder database instead of the GUID of the Exchange 2010 public folder server. When Exchange 2003 looks up the database GUID to assign cost, it’s not a valid server path. Therefore, it’s marked with an infinite cost. Because the cost is infinite, it doesn’t refer the client to the Exchange 2010 server.

To resolve this issue, use Active Directory Service Interfaces Editor (ADSI Edit) to modify the msExchfolderAffinityList attribute on the Exchange 2003 server. Specifically, replace the GUID of the Exchange 2010 public folder database with the GUID of the Exchange 2010 public folder server.

To do this, follow these steps on the Exchange 2003 server.

1. Open Exchange Management Shell, and then follow these steps:
   1. Identify the GUID of the Exchange 2010 public folder database. To do this, run the following command:

      get-publicfolderdatabase |fl name, guid

   2. Identify the GUID of the Exchange 2010 public folder server. To do this, run the following command:

      get-exchangeserver |fl name,guid

2. Use ADSI Edit to locate the msExchfolderAffinityList attribute, and then specify the GUID of the Exchange 2010 public folder server.
   1. Open ADSI Edit, and then connect to the Configuration context.
   2. Expand the domain, and then locate the server.

      The path of the server is Configuration/Services/Microsoft Exchange//Administrative groups/Servers/.

   3. Right-click the server, and then click Properties.
   4. Click the Attribute Editor tab, locate and then select the msExchfolderAffinityListattribute.
   5. Click Edit, and then based on the information that you obtained in step 1, replace the GUID of the Exchange 2010 public folder database with the GUID of the Exchange 2010 public folder server.
3. Restart the Microsoft Exchange Information Store service. For more info about how to do this, go to the following Microsoft website:

After you follow this procedure, the Exchange 2010 public folder server name will show in the custom list for public folder referrals. Note that you can modify the other servers in the custom list without affecting the updated GUID in the msExchFolderAffinityList attribute.

The msExchfolderAffinityList attribute is the Active Directory property that resolves the custom list for public folder referrals to server GUIDs. 

For more information, see the following Microsoft resources:

Article ID: 2847591 – Last Review: May 17, 2013 – Revision: 1.0

A current Deployment Administrator may be unable to add a new Deployment Administrator from a trusted domain

When adding a user from another domain as a Deployment Administrator, you are able to find that user in the UserPickerForm, but only after the current signed in Deployment Administrator enters credentials to be able to browse the object in the trusted domain. Once the user is chosen and we retrieve the user properties with an LDAP call, the credentials are lost and reverted back to the CRM domain credentials (local deployment administrator credentials without access to the trusted domain). This causes the LDAP call to not find any users and a null value is returned for the user. This simulates that the user cancelled out of the wizard.

1. Create a two-way trust between the domains in order to add the user as a new Deployment Administrator.

2. Manage the username and password prior to assigning it as a Deployment Administrator. To do this:

a. Go to Manage your Network Passwords on the server and have the current Deployment Administrator add the Domain Controller and credentials from the trusted domain. This allows the credentials to be automatically passed for the LDAP query and not dropped.

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: 2842571 – Last Review: May 17, 2013 – Revision: 3.0