KB Articles

Page 1 of 98812345...102030...Last »

"Inbound Connector doesn’t exist" error when you run the Hybrid Configuration wizard to upgrade an Exchange 2010 SP3-based hybrid deployment to Exchange 2013

When you try to upgrade an Exchange Server 2010 Service Pack 3 (SP3)-based hybrid deployment to an Exchange Server 2013-based hybrid deployment, the upgrade doesn’t complete successfully. You receive the following error message in the Hybrid Configuration wizard:
The wizard did not complete successfully. Please see the list below for error details.

Updating hybrid configuration failed with error ‘Subtask Configure execution failed: Upgrading hybrid configuration from Exchange 2010… Execution of the New-OnPremisesOrganization cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings. Inbound Connector ‘domain.onmicrosoft.comHybrid Mail Flow Inbound Connector’ doesn’t exist.

This issue persists even after you rename the connector.

This issue occurs because of a compatibility issue with how the objects were created in the two environments.
To resolve this issue, follow these steps:
  1. On the Exchange 2013 server, open the Exchange Management Shell, and then run the following command:
    Remove-HybridConfiguration
  2. Remove the two hybrid connectors in the Exchange admin center in Exchange Online. To do this, follow these steps:
    1. Sign in to the Office 365 portal, click Admin, and then click Exchange.
    2. In the Exchange admin center, click mail flow, and then click connectors.
    3. In the list of connectors, select the hybrid connector, and then click Delete (

      Collapse this imageExpand this image

      ).

      Note These connectors are typically named “Inbound from ” and “Outbound to “.

      Collapse this imageExpand this image

  3. Rerun the Hybrid Configuration wizard on the Exchange 2013 server.

Note During the time between when the connectors are removed and when the Hybrid Configuration wizard is run, you will lose rich coexistence with regards to mail flow. However, mail will still route through the MX record to its destination. If you have centralized mail control routing enabled, mail will route out to the Internet and not to your on-premises server until the Hybrid Configuration wizard is successfully run on the Exchange 2013 server.

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 3047374 – Last Review: April 24, 2015 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365022013 o365 o365a hybrid kbgraphic kbgraphxlink KB3047374

Read More:
"Inbound Connector doesn’t exist" error when you run the Hybrid Configuration wizard to upgrade an Exchange 2010 SP3-based hybrid deployment to Exchange 2013

How to add the ‘Display Calc Work Records’ shortcut in Canadian Payroll for Microsoft Dynamics GP

You can add a shortcut to view the calculated work records for the calculated batch in Canadian Payroll.  This information can be viewed any time after the batch is calculated, and is overwritten when the next batch is calculated.
Use these steps to add the shortcut:

1. In Microsoft Dynamics GP, click on the HOME area page.

2. Right-click on Shortcuts in the left navigation pane.

3. Click Add

4. Click Add Window

5. In the Add Window Shortcut window, click to expand Canadian Payroll, and click to expand Project.

6. Scroll down and click on WORK – Display Calc Work Records

7. Click Done. (Click Yes if prompted to save changes.)

Now click on Shortcuts again in the left navigation pane and you will see WORK-Display Calc Work Records listed. Click to open it. Enter the Employee ID. You will be able to see all the calculated amounts from the last payrun including Federal/Provincial tax information, T4/T4A/R1 information, CPP/EI information, Taxable/Before Tax and After tax information, SCB, RRSP, EHT, GST, Banked Information for paid and accumulated, and Vacation-paid and accrued.

This information is still available to view after you post, so you can view what was on the last payrun. It will be overwritten when the next payroll batch is calculated. 
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: 3060712 – Last Review: April 23, 2015 – Revision: 3.0


Applies to
  • Microsoft Dynamics GP 2015
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0, when used with:
kbmbsmigrate kbsurveynew KB3060712

Excerpt from:
How to add the ‘Display Calc Work Records’ shortcut in Canadian Payroll for Microsoft Dynamics GP

FIX: Pipeline errors occur when you use BAM tracking in BizTalk Server 2010 CU7

When you use the Business Activity Monitoring (BAM) tracking profile in Microsoft BizTalk Server 2010 Cumulative Update 7 (CU7), the following event entries for pipeline errors are logged in the Application log:
Log Name: Application
Source: BizTalk Server
Date:  

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

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

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

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

Prerequisites

To apply this hotfix, you must install the BizTalk Server 2010 Cumulative Update 7 (CU7).

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

Article ID: 3047071 – Last Review: April 22, 2015 – Revision: 1.0


Applies to
  • Microsoft BizTalk Server Branch 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Standard 2010
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB3047071

Link:
FIX: Pipeline errors occur when you use BAM tracking in BizTalk Server 2010 CU7

"The user isn’t assigned to any management roles" error when you run the Hybrid Configuration wizard

ERROR:Updating hybrid configuration failed with error ‘System.Management.Automation.Remoting.PSRemotingTransportException: Processing data from remote server failed with the following error message: The user “<>/Users/Administrator” isn’t assigned to any management roles. For more information, see the about_Remote_Troubleshooting Help topic.

Read the article:
"The user isn’t assigned to any management roles" error when you run the Hybrid Configuration wizard

"Secure Mail Certificate on server is not bound to the SMTP Service" error when you run the Hybrid Configuration wizard

[] ERROR:Updating hybrid configuration failed with error ‘Subtask CheckPrereqs execution failed: Configure Mail Flow

The Secure Mail Certificate on server is not bound to the SMTP Service
at Microsoft.Exchange.Management.Hybrid.MailFlowTask.CheckCertPrereqs

See the original post:
"Secure Mail Certificate on server is not bound to the SMTP Service" error when you run the Hybrid Configuration wizard

Exchange Online users cannot access free/busy information of users in a non-Internet-facing Active Directory site

Log Name: Application
Source: MSExchange Availability
Event ID: 4002
Task Category: Availability Service
Level: Error
Keywords: Classic
User: N/A
Computer: .domain.com
Description:
Process 6424: ProxyWebRequest CrossSite from UserA@contoso.mail.onmicrosoft.com to
https://:443/ews/exchange.asmx failed.
Caller SIDs: WSSecurity. The exception returned is
Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
—> System.IO.IOException: Unable to read data from the transport connection: An existing connection
was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection
was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)
at System.Net.TlsStream.EndRead(IAsyncResult asyncResult)
at System.Net.PooledStream.EndRead(IAsyncResult asyncResult)
at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()
at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult,
Object& internalAsyncState, Stream& responseStream)
at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest
proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling(): response>. The request information is
ProxyWebRequest type = CrossSite, url = https://FQDN of
Non-Internet facing Exchange>:443/ews/exchange.asmx
Mailbox list = SMTP:UserB@fabrikam.com, Parameters: windowStart = 3/8/2015 1:00:00 PM,
windowEnd = 4/7/2015 1:00:00 PM, MergedFBInterval = 30, RequestedView = Detailed
. —> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on
a receive. —> System.IO.IOException: Unable to read data from the transport connection: An existing
connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing
connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)
at System.Net.TlsStream.EndRead(IAsyncResult asyncResult)
at System.Net.PooledStream.EndRead(IAsyncResult asyncResult)
at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()
at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult,
Object& internalAsyncState, Stream& responseStream)
at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest
(ProxyWebRequest proxyWebRequest,
QueryList queryList, Service service, IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
— End of inner exception stack trace —
. Name of the server where exception originated: .

Visit site:
Exchange Online users cannot access free/busy information of users in a non-Internet-facing Active Directory site

How to use Outlook policy to control PST use and creation in the Office 365 Import service

When you use the Microsoft Office 365 Import service, you may want to control whether users can add new items to .pst files and how users use .pst files in Microsoft Outlook. This article describes how to prevent users from adding new items to an existing .pst file and how to prevent users from creating new .pst files during the import process.
Important Follow the steps in this article carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration

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

in case problems occur.

Prevent users from adding new data or content to an existing .pst file

Collapse this imageExpand this image

To prevent users from adding new data or content to an existing .pst file, add the PSTDisableGrow registry entry, and then set the value to 1. To do this, follow these steps:

  1. Open Registry Editor.
  2. Locate, and then click the following registry subkey:

    HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice<x>.0OutlookPST

    Note The <x>.0 placeholder represents the version of Outlook: for example, 15.0 is Outlook 2013, 14.0 is Outlook 2010, and 12.0 is Outlook 2007.

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type PSTDisableGrow, and then press Enter.
  5. Right-click the PSTDisableGrow registry entry that you created, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

Note The PSTDisableGrow registry entry can be set to the following values:

Collapse this tableExpand this table

Value Description
0 User can add new items to an existing .pst file. This is the default value.
1 Use cannot add new content or data to an existing .pst file

Collapse this imageExpand this image

Prevent users from adding new .pst files

Collapse this imageExpand this image

To prevent users from connecting a .pst file to Outlook, add the DisablePST registry entry, and then set the value to 1. To do this, follow these steps:

  1. Open Registry Editor.
  2. Locate, and then click the following registry subkey:

    HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice.0Outlook

    Note The <x>.0 placeholder represents the version of Outlook: for example, 15.0 is Outlook 2013, 14.0 is Outlook 2010, and 12.0 is Outlook 2007.

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type DisablePST, and then press Enter.
  5. Right-click the DisablePST registry entry that you created, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

Note The DisablePST registry entry can be set to the following values:

Collapse this tableExpand this table

Value Description
0 Users can add .pst files. This is the default value.
1 Users cannot add .pst files.
However, in scenarios where a .pst file was connected to Outlook before this registry value was added, the existing .pst file will still be connected. No new.pst files can be added.
2 Users can only add exclusive sharing .pst files, such as SharePoint .pst files.

Collapse this imageExpand this image

Article ID: 3058474 – Last Review: April 21, 2015 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Outlook 2013
  • Microsoft Outlook 2010
  • Microsoft Office Outlook 2007
o365e o365m o365022013 o365 o365a KB3058474

Visit link:
How to use Outlook policy to control PST use and creation in the Office 365 Import service

Exchange Online users are unable to access free/busy information of users on a non-Internet-facing Active Directory site

Log Name: Application
Source: MSExchange Availability
Event ID: 4002
Task Category: Availability Service
Level: Error
Keywords: Classic
User: N/A
Computer: .domain.com
Description:
Process 6424: ProxyWebRequest CrossSite from UserA@contoso.mail.onmicrosoft.com to https://:443/ews/exchange.asmx failed. Caller SIDs: WSSecurity. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)
at System.Net.TlsStream.EndRead(IAsyncResult asyncResult)
at System.Net.PooledStream.EndRead(IAsyncResult asyncResult)
at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()
at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult, Object& internalAsyncState, Stream& responseStream)
at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling():. The request information is ProxyWebRequest type = CrossSite, url = https://FQDN of Non-Internet facing Exchange>:443/ews/exchange.asmx
Mailbox list = SMTP:UserB@fabrikam.com, Parameters: windowStart = 3/8/2015 1:00:00 PM, windowEnd = 4/7/2015 1:00:00 PM, MergedFBInterval = 30, RequestedView = Detailed
. —> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)
at System.Net.TlsStream.EndRead(IAsyncResult asyncResult)
at System.Net.PooledStream.EndRead(IAsyncResult asyncResult)
at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()
at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult, Object& internalAsyncState, Stream& responseStream)
at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
— End of inner exception stack trace —
. Name of the server where exception originated: . Make sure that the Active Directory site/forest that contain the user’s mailbox has at least one local Exchange server running the Availability service. Turn up logging for the Availability service and test basic network connectivity.

See original article:
Exchange Online users are unable to access free/busy information of users on a non-Internet-facing Active Directory site

How to use Outlook policy to control PST use and creation when you use the Office 365 Import service

When you use the Microsoft Office 365 Import service, you may want to control whether users can add new items to .pst files and how users use .pst files in Microsoft Outlook. This article describes how to prevent users from adding new items to an existing .pst file and how to prevent users from creating new .pst files during the import process.
Important Follow the steps in this article carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration

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

in case problems occur.

Prevent users from adding new data or content to an existing .pst file

Collapse this imageExpand this image

To prevent users from adding new data or content to an existing .pst file, add the PSTDisableGrow registry entry, and then set the value to 1. To do this, follow these steps:

  1. Open Registry Editor.
  2. Locate, and then click the following registry subkey:

    HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice.0OutlookPST

    Note .0 represents the version of Outlook, in which 15.0 is Outlook 2013, 14.0 is Outlook 2010, and 12.0 is Outlook 2007.

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type PSTDisableGrow, and then press Enter.
  5. Right-click the PSTDisableGrow registry entry that you created, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

Note The PSTDisableGrow registry entry can be set to the following values:

Collapse this tableExpand this table

Value Description
0 User can add new items to an existing .pst file. This is the default value.
1 Use cannot add new content or data to an existing .pst file

Collapse this imageExpand this image

Prevent users from adding new .pst files

Collapse this imageExpand this image

To prevent users from connecting a .pst file to Outlook, add the DisablePST registry entry, and then set the value to 1. To do this, follow these steps:

  1. Open Registry Editor.
  2. Locate, and then click the following registry subkey:

    HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice.0Outlook

    Note .0 represents the version of Outlook, in which 15.0 is Outlook 2013, 14.0 is Outlook 2010, and 12.0 is Outlook 2007.

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type DisablePST, and then press Enter.
  5. Right-click the DisablePST registry entry that you created, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

Note The DisablePST registry entry can be set to the following values:

Collapse this tableExpand this table

Value Description
0 Users can add .pst files. This is the default value.
1 Users cannot add .pst files.
However, in scenarios where a .pst file was connected to Outlook before this registry value was added, the existing .pst file will still be connected. No new.pst files can be added.
2 Users can only add exclusive sharing .pst files, such as SharePoint .pst files.

Collapse this imageExpand this image

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: 3058474 – Last Review: April 21, 2015 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Outlook 2013
  • Microsoft Outlook 2010
  • Microsoft Office Outlook 2007
o365e o365m o365022013 o365 o365a KB3058474

Continue Reading:
How to use Outlook policy to control PST use and creation when you use the Office 365 Import service

How to void an AR type cash receipt in Cashbook Management in Microsoft Dynamics GP

This article explains how to void an ‘AR’ type cash receipt in Cashbook Bank Management using Microsoft Dynamics GP. The cash receipt is listed in the Build Deposits Entry window in Cashbook Management and there is no way to delete it in this window. If you deposit it in Cashbook Management and then try to delete this deposit in the Transaction Enquiry/Void window, you will get the message:

This deposit is an AR transaction and cannot be voided from the Bank Recon.

By design.  Since it was an ‘AR’ type cash receipt and updated Receivables Management, the system now considers it to have originated from Receivables Management, and there is no functionality to void the cash receipt in Cashbook Management.
When you post a cash receipt in Cashbook Bank Management, it will create a cash receipt batch in Receivables Management. Depending on what you do with that cash receipt batch in Receivables Management, follow the appropriate method below for voiding the cash receipt:
  • The recommended process is to post the cash receipt batch in Receivables Management and deposit the cash receipt in Cashbook Management. Then void the posted cash receipt in Receivables Management under Posted Transactions. The void will flow back to Cashbook Management, and will be listed in the Transaction Enquiry/Void window as a negative amount, to serve as an offset to the deposit for the cash receipt in Cashbook Management. Both the negative amount and deposit will be listed in the Transaction Enquiry/Void window to offset each other. This is the intended design. 
  • Now if you would delete the cash receipt batch in Receivables Management, then you do not have a way to void the cash receipt that is in Cashbook Management. If you deposit it in Cashbook Management and then try to void the deposit, you will get the message indicated above. At this point, the only way to remove the cash receipt from the Build Deposits window in Cashbook Management is to remove it from the following SQL tables (which is not a recommended or supported option): 

CB100000
CB100003
CB100011
CB330222
CB990007 –this is the table that actually drops it off the Build Deposits window
CB220210
CB600066

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: 3058407 – Last Review: April 20, 2015 – Revision: 2.0


Applies to
  • Microsoft Dynamics GP 2015
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0, when used with:
kbmbsmigrate kbsurveynew KB3058407

Original post:
How to void an AR type cash receipt in Cashbook Management in Microsoft Dynamics GP

Page 1 of 98812345...102030...Last »

Recent Comments

    Archives

    Categories