Page 323 of 752« First...102030...321322323324325...330340350...Last »

Setup information for Electronic Reconcile Format Configurator

SUMMARY

This article contains information about setting up the Electronic Reconcile Configurator.

MORE INFORMATION


General Setup for Electronic Reconcile Format Configurator

The process of setting up the Format Configurator in Electronic Reconcile is very lengthy and the following detailed steps will help to make this setup easier. Before setting up the Format Configurator, you must have a printed copy of the download file format specifications from your bank. Because bank formats vary greatly, you must contact your bank and request these specifications for the file format. The format specifications will contain details about each field being downloaded and values of all relevant codes for the bank. This information is necessary to be able to setup the Format Configurator as each bank is different and there is no standard format to enter.

Electronic Reconcile Format Configurator (Routines | Financial | Electronic Reconcile | Configurator):

Section 1 – Enter Format Information

Bank Format – The Bank Format field is an identifier for your format. Enter a unique name for this format, but typically this is the name of your Bank.

Description – The Description field is used to enter an additional description for the Bank Format.

File Format – The File Format field can be selected from the drop-down list as Fixed Field, Comma Delimited, or Tab Delimited. The bank determines which option from the list that you will select. Therefore, you must contact them if the format specifications do not state the format to use.

Uses Status Codes – The Uses Status Codes option is marked only if your bank uses Status Codes to additionally define Transaction Codes. This information is also determined by each bank. Therefore, if the format specifications do not state if your bank uses Status Codes, you must contact the bank. (This is not used very often.)

Record Type Identifier – The Record Type Identifier will contain Start Position and End Position fields if you are using the Fixed Field format and a Field Number field if you are using Comma Delimited or Tab Delimited file formats. This will be where the system should look in the line to determine what type of line (header, footer or detail) it is. If the bank doesn’t use a record type code, then you can improvise by selecting a fixed value in the file.

-Fixed Field – Enter the starting and ending position of the field that will contain the value for the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

-Comma Delimited or Tab Delimited – Enter the number of the field that contains the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

Save the Format after Section 1 has been completed before moving on to Section 2 of the Electronic Reconcile Format Configurator window.

Section 2 – Enter Record Types


Note You will only have to define the Record Types that are relevant to Electronic Reconcile. If a section is labeled as optional on the bank specifications, you do not have to set it up in the Format Configurator. The Detail Record Type is always a required section in a bank’s specifications.

Bank ID – The Bank ID will default in with the Bank Format from section 1 as soon as you tab into the Record Type field in the second section. This field cannot be changed or edited.

Record Type – The Record Type field can be selected from the drop-down list as Header, Detail, or Footer. All bank formats will require a Detail Record Type, but the header and footer Record Types may be optional. You may only setup each of the Record Types one time as multiple headers or footers are not available.

Record Type Code from Bank – The Record Type Code from Bank field is defined in your bank’s specifications. This field must be a unique and constant identifier for the format to match the information in the Detail Record Type. This is the most important field in setting up the Format Configurator to correctly match the download file with the reconciliation.

# of fields – The number of fields indicates how many fields are to be defined in Section 3. Enter the number of fields contained on the line for the Record Type being defined. This information must be entered for each Record Type that is required in the bank’s specifications.

Section 3 – Enter Field Information

Note Just as with Record Types, you will only have to define the fields that are relevant to Electronic Reconcile. If there is a field on the bank’s specifications that cannot be defined with an existing Record Type or does not have to be defined, use the Filler/Ignore option.

Record Type – The Record Type field in the left-most column of Section 3 will default in when you select a Record Type from the drop-down list in the upper right corner of this section. Select from the options of Header, Detail, Footer, or All in the drop-down list and if you select All, then each of the Record Types that you setup in Section 2 will appear in Section 3 to be defined.

# – The number field will default in with the number of fields that you entered in Section 2 for the Record Type that has been selected in Section 3. They will increment numerically and will start over with 1 each time a new Record Type is listed if using the Record Type of All.

Field Type – The Field Type field is used to define each of the relevant fields for each of the Record Types. Select the Field Type from the drop-down list that includes options for Accounts, Dates, and amounts. If the exact name of your field from your bank’s specifications does not appear in the list, you may have to either select an option that is similar or use the Filler/Ignore option. Again, you only need to define the relevant fields, most importantly: Account Numbers, Check Numbers, Check Dates, Check amounts, Transaction Codes, Record Type Codes, etc.

Format – The Format field defines the type of output format for certain fields. Formats only have to be set for Field Types that contain dates or a currency amount, as these are the only options for Formats. There are no options for text or string. Therefore, if the field is not a date or a currency amount, just leave the Format field blank. The From and To fields are used to enter the character positions of the field. Enter the starting and ending character position for each field in each Record Type. The From and To fields must be entered if using the Fixed Field File Format, so if you are using Tab Delimited or Comma Delimited File Formats you can leave these fields as zero.

Transaction Codes (Codes Entry – Transaction Codes Entry)

While still in the Electronic Reconcile Format Configurator window, go in the Transaction Codes Entry window through the path earlier in this article from the top Menu Bar. If you have not defined the Transaction codes, you will get the message “Record Type match not found” on the error report.

Transaction Codes identify the type of transaction that each Detail line represents. Electronic Reconcile requires a Transaction Code in a configured Bank Format to work correctly. You must have Transaction Codes or Record Type Codes defined to use Electronic Reconcile. These codes must come from the bank and must be listed on the bank’s specifications.

Transaction Type – The Transaction Type field is used to define each of the different types of transactions that appear on your bank’s specifications. Select a Transaction Type from the list to match or to closely match your bank’s specifications. Note that the options in the list are the only currently supported types. At this time, the two supported options are Check Paid and Deposit Cleared.

Transaction Type Code – The Transaction Type Code field is used to enter the value for each Transaction Type and this value is given to you as part of the file specifications from your bank. Enter the Transaction Type Code value that corresponds to the selected Transaction Type. This information must come from the bank and cannot be improvised if it is not available on the bank’s specifications.

G/L Account – The G/L Account field is available only for the following Transaction Types: Interest Income, Other Income, Other Expense, and Service Charge. Enter the G/L Account Number of a General Ledger Posting Account for the adjustment that will be generated. Electronic Reconcile will automatically create adjustments for these transaction types if they appear in the downloaded file from your bank.

Note Because the Interest Income, Other Income, Other Expense, and Service Charge transaction types are currently unsupported, this is not a feature that is currently in Microsoft Dynamics GP.

Account Description – The Account Description field will default in with the description of your account as you set it up in General Ledger. It is not editable in Electronic Reconcile.

Distribution Reference – The Distribution Reference field can be used to enter an additional reference for the adjustment that will be made. You can enter a Distribution Reference if you want, but it is not a required field.

Document Type – The Document Type field will default in with the Transaction Type that you selected at the top of the Transaction Code Entry window: Interest Income, Other Income, Other Expense, or Service Charge. This field cannot be changed unless you go back and change the Transaction Type field.

Define Status Codes – The Define Status Codes button only becomes available if you have marked the Uses Status Codes option in the Electronic Reconcile Format Configurator window. Define Status Codes is only available for certain Transaction Types: Check Paid and Deposit Cleared. After selecting one of these 2 Transaction Types, you would select the Define Status Codes button to go into the Status Codes Entry window. Here you would select: Paid Check, Check Reversal, Stop Pay, or Stop Pay Reversal for the Status Type and enter the corresponding Status Code from your bank’s specifications. Again this information has to come from your bank and cannot be improvised or Electronic Reconcile will not work correctly.

Special notes to remember when setting up Electronic Reconcile:

  • You must have a printout of the file format specifications from your bank before setting up the Electronic Reconcile Format Configurator.
  • Every bank is different. Therefore, you cannot follow one standard format for all banks.
  • If you open the .TXT or .CSV file with Notepad, the system will typically not read any information after position 245. So make sure all the required fields to be mapped are in the first part of the line if your lines are more than 245 characters. The information after 245 will be read as a new line and appear on the Unprocessed Data Record error report as “Record Type match not found: Record Type = ” because there isn’t one. This would be acceptable if no fields after position 245 are not needed. If there are fields that are needed, you will need to contact your bank to see if they are able to reconfigure the file to be smaller and not exceed 245 characters.
  • The Electronic Reconcile Format Configurator only needs to be setup once when first starting to use Electronic Reconcile, and then you just keep downloading .TXT or .CSV files from the bank to match this Format Configurator.
  • The following fields must be present in your bank format: Transaction Code, Account Number, Check/Serial Number, Transaction Amount, Record Type Code, and the Bank Cleared Date. If your format uses Status Codes, then the Transaction Status Code must also be present in the configuration.
  • If you have gone through all of the Electronic Reconcile process and no transactions are marked off as cleared in your Bank Reconciliation module, most likely something is not set up correctly in the Electronic Reconcile Format Configurator. The most common error message that will be received is a “Record Type Match Not Found” error on the Unprocessed Records report that prints after trying to download.
  • If you try to re-download after you have already downloaded the .txt file from the bank, you will receive “Duplicate” error messages because the system sees the transactions as duplicates instead of just downloading new transactions.
  • If you try to delete a Reconcile and re-enter the information after you have already downloaded the .txt file from the bank, you will receive “Duplicate” error messages because the system sees the transactions as duplicates.
  • Make sure the Bank Account Number is unique for the checkbook that is set up with Electronic Reconcile. If the Bank Account Number is set up with a different checkbook, Electronic Reconcile will not be able to match the downloaded transactions and you will receive a message stating that the Bank Account Number is not set up.
  • If you enter an increase adjustment or a decrease adjustment in the Reconcile Bank Adjustments window, the following adjustment types create an adjustment transaction in the Reconciliation Bank Adjustments window:
    • Interest Income
    • Other Income
    • Other Expense
    • Service Charge
  • If you enter an increase adjustment, a decrease adjustment, or a withdrawal in the Bank Transaction Entry window, you are prompted to manually mark the adjustment. When you receive this message, you must manually mark the records in the configurator file.

This article was TechKnowledge Document ID: 19396

Read this article:
Setup information for Electronic Reconcile Format Configurator

Purchase button does not show in Fixed Asset General Information window in Microsoft Dynamics GP

The Purchase button is missing from the Fixed Asset General Information window in Microsoft Dynamics GP.
The setup is not complete.  See Resolution section below.
There are 5 requirements to have Payables interface with Fixed Assets, and the Purchase button to appear on the Fixed Asset General Information window:

1. On the Microsoft Dynamics GP menu, click on Tools, point to Setup, point to Fixed Assets and click Company. Make sure the Post PM through to FA checkbox is marked.

2. Also on the Fixed Assets Company Setup window, make sure the Require Account checkbox is marked.

3. On the Microsoft Dynamics GP menu, click on Tools, point to Setup, point to Fixed Assets and click Purchase Posting Accounts. Click the Lookup button next to the Account number field and make sure a GL account has been specified.  The accounts listed here will be the trigger accounts to interface Purchasing with Fixed Assets.

4. Fixed Assets must be installed on that particular workstation.

5. When entering the transaction in Payables Transaction Entry, click on the Distributions button. The trigger account must be keyed in the PURCH line and a debit to the trigger account (from step 3). Post the transaction in Payables. 

Now when you go to the Asset General Information window in Fixed Assets, the Purchase button will show. However, first you must enter the Asset ID and suffix, then click the Purchase button and mark the checkbox for the purchases document you wish and click Select to have it populate the Asset General Information window.
 

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: 2761966 – Last Review: September 26, 2012 – Revision: 2.0


Applies to
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0, when used with:
    • Fixed Asset Management
    • Fixed Assets
kbmbsmigrate kbsurveynew KB2761966

Originally posted here:
Purchase button does not show in Fixed Asset General Information window in Microsoft Dynamics GP

The file replication is unsuccessful when you try to replicate a file that is larger than 2 GB by using Application Center 2000 Service Pack 2 on a computer that is running Windows Server 2003

When you try to replicate a file by using Microsoft Application Center 2000 Service Pack 2 (SP2) on a computer that is running Microsoft Windows Server 2003, the file replication is unsuccessful. This problem occurs when the file is larger than 2 gigabytes (GB).
This problem occurs because the Windows Sockets TransmitFile function that the Application Center 2000 Replication Service (Acsrepl.exe) calls does not support transmitting files that are larger than 2 GB.
To work around this problem, use one of the following methods:
  • If you do not have to have the file on each cluster member, put the file that is larger than 2 GB on a Universal Naming Convention (UNC) share.
  • If you have to have the file on all cluster members, use Xcopy.exe to copy the file to all nodes in the cluster. Then, exclude the file from the Application Center 2000 replication.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about how to use Xcopy.exe, visit the following Microsoft Web site:

Article ID: 904936 – Last Review: September 26, 2012 – Revision: 2.0


Applies to
  • Microsoft Application Center 2000 Service Pack 2
kbtshoot kbnofix kbbug kbprb KB904936

Continue reading here:
The file replication is unsuccessful when you try to replicate a file that is larger than 2 GB by using Application Center 2000 Service Pack 2 on a computer that is running Windows Server 2003

The "Account only" copy option of versions and of input sets does not work in Microsoft Forecaster

unable to retrieve full-text content

Read the original:
The "Account only" copy option of versions and of input sets does not work in Microsoft Forecaster

Extender fields are not imported when you import data for an Extender window in Microsoft Dynamics GP 9.0 Service Pack 3

When you import data for an Extender window in Microsoft Dynamics GP 9.0 Service Pack 3, Extender fields are not imported.
To resolve this problem, obtain the latest service pack for Microsoft Microsoft Dynamics GP 9.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

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 Dynamics GP 9.0 Service Pack 4.
To download the most recent Microsoft Windows Installer update (MSP) file for Microsoft Dynamics GP, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer:

Partners

Customers

Article ID: 948264 – Last Review: September 26, 2012 – Revision: 6.0


Applies to
  • Microsoft Dynamics GP 9.0
  • Extender
kbexpertiseadvanced kbtshoot kbmbsmigrate kbbug KB948264

Read the article:
Extender fields are not imported when you import data for an Extender window in Microsoft Dynamics GP 9.0 Service Pack 3

The SmartList object displays the data from the current company, and the SmartList object repeats the data multiple times in Microsoft Dynamics GP 9.0

In Microsoft Dynamics GP 9.0, you create a SmartList object, and then you click to select the Multicompany SmartList check box. After you do this, the SmartList object displays the data from the current company, and the SmartList object repeats the data multiple times.

For example, if you select two companies when you create the SmartList object, the SmartList object repeats the data from the current company two times.

You expect the SmartList object to display the data from the different companies that you select.

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

Partners

Customers

This problem still occurs in Microsoft Dynamics GP 9.0. This problem was first corrected in Microsoft Dynamics GP 10.0 Service Pack 2.

Article ID: 944442 – Last Review: September 26, 2012 – Revision: 6.0


Applies to
  • Microsoft Dynamics GP 9.0
  • SmartList Builder
kbtshoot kbexpertisebeginner kbmbsmigrate kbprb kbexpertiseinter KB944442

See the original post:
The SmartList object displays the data from the current company, and the SmartList object repeats the data multiple times in Microsoft Dynamics GP 9.0

Error message when you post to reverse a manufacturing order receipt in Microsoft Dynamics GP 10.0: "An error occurred while saving transaction line. Check the data and try again"

When you post a manufacturing
order
receipt in Microsoft Dynamics GP 10.0, components of the finished goods are back-flushed. Then, you try to post to reverse the manufacturing
order
receipt. This action puts the components back into the inventory to adjust the inventory. However, when you post to reverse the manufacturing order receipt,
you receive the following error message:

An error occurred
while saving transaction line. Check the data and try
again.

This problem occurs because the inventory adjustment may contain incorrect component quantities when you post to reverse the manufacturing order receipt.

Service pack information

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

Partners

Customers

Hotfix information

To resolve this problem, apply hotfix rollup 948474.

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

948474

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

Hotfix rollup 948474 is now available for the English version of Microsoft Dynamics GP 10.0

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 Dynamics GP 10.0 Service Pack 3.

Article ID: 950017 – Last Review: September 26, 2012 – Revision: 5.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Manufacturing
kberrmsg kbexpertisebeginner kbtshoot kbmbsmigrate kbprb kbexpertiseinter KB950017

Original post:
Error message when you post to reverse a manufacturing order receipt in Microsoft Dynamics GP 10.0: "An error occurred while saving transaction line. Check the data and try again"

Error message when you try to delete a Sales Order Processing batch in Microsoft Dynamics GP: "Unhandled script exception: Illegal address for field ‘Customer Number’ in script ‘vatDaybook_SOPRemoveRC’"

Consider the following scenario. You upgrade to Microsoft Dynamics GP 9.0 Service Pack 3 or to a later version of Microsoft Dynamics GP. Then, you try to delete a Sales Order Processing (SOP) batch. In this scenario, you receive the following error message:

Unhandled script exception: Illegal address for field ‘Customer Number’ in script ‘vatDaybook_SOPRemoveRC’. Script terminated.

Therefore, you cannot delete the SOP batch.

However, you can delete the SOP batch if you uninstall VAT Daybook in Microsoft Dynamics GP.

This problem occurs if the following conditions are true:

  • The country code that you use is GB.
  • You use the reverse charge tax.

This problem occurs because Microsoft Dynamics GP calls the vatDaybook_SOPRemoveRC script. However, the vatDaybook_SOPRemoveRC script does not exist. When Microsoft Dynamics GP runs the following code, this problem occurs.
sp_helptext vatDaybook_SOPRemoveRC

Microsoft Dynamics GP 10.0

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

Partners

Customers

Microsoft Dynamics GP 9.0

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

Partners

Customers

To work around this problem, delete the transactions that are assigned to the SOP batch in the Sales Transaction Entry window. To do this, follow these steps:
  1. On the Transactions menu, point to Sales, and then click Sales Transaction Entry.
  2. In the Document No list, click a document number that is assigned to the SOP batch.
  3. Follow the appropriate step:
    • In Microsoft Dynamics GP 10.0, click Actions, and then click Delete.
    • In Microsoft Dynamics GP 9.0, click Delete.
  4. When you are prompted to delete the transaction, click Delete.
  5. Repeat steps 2 through 4 for each transaction that is assigned to the SOP batch.

Microsoft Dynamics GP 10.0

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 Dynamics GP 10.0 Service Pack 2.

Microsoft Dynamics GP 9.0

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 Dynamics GP 9.0 Service Pack 4.

Article ID: 952213 – Last Review: September 26, 2012 – Revision: 5.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Sales Order Processing
kbmbsvatdaybookeurope kberrmsg kbexpertisebeginner kbtshoot kbmbsmigrate kbbug kbexpertiseinter KB952213

Visit link:
Error message when you try to delete a Sales Order Processing batch in Microsoft Dynamics GP: "Unhandled script exception: Illegal address for field ‘Customer Number’ in script ‘vatDaybook_SOPRemoveRC’"

Error message when you try to install Dexterity or the Visual Studio Tools for Microsoft Dynamics GP 10.0 SDK: ".NET Framework 2.0 is not detected. Fatal error during installation"

When you try to install Dexterity for Microsoft Dynamics GP 10.0 or the Microsoft Visual Studio Tools for Microsoft Dynamics GP 10.0 Software Development Kit (SDK), you receive the following error message:

.NET Framework 2.0 is not detected. Fatal error during installation.

Additionally, the installation process stops.

This problem occurs if the Microsoft .NET Framework 2.0 Service Pack 1 (SP1) is installed on the computer.
To resolve this problem, obtain the latest service pack for Microsoft Dynamics GP 10.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

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

Method 1:
If you encounter this problem when you try to install Dexterity

To work around this problem, follow these steps:

  1. Download the SkipDotNetCheckDexterity.mst file.

    The following file is available for download from the Microsoft Dynamics File Exchange Server:

    Release Date: April 15, 2008

    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

  2. Copy the SkipDotNetCheckDexterity.mst file to the root directory of drive C.
  3. Click Start, click Run, type cmd, and then click OK.
  4. At the command prompt, type cd, and then press ENTER.
  5. At the command prompt, type the following command, and then press ENTER:

    msiexec /i “ ” TRANSFORMS=”C:SkipDotNetCheckDexterity.mst” INSTALLDIR=”” /qb+

    Notes

  6. At the command prompt, type exit, and then press ENTER.

After you follow these steps, Dexterity is installed in the location that you specify in step 5. The default installation includes all the features of Dexterity.

Method 2:
If you encounter this problem when you try to install the Visual Studio Tools for Microsoft Dynamics GP 10.0 SDK

To work around this problem, follow these steps:

  1. Download the SkipDotNetCheckVSTools.mst file.

    The following file is available for download from the Microsoft Dynamics File Exchange Server:

    Release Date: April 15, 2008

    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

  2. Copy the SkipDotNetCheckVSTools.mst file to the root directory of drive C.
  3. Click Start, click Run, type cmd, and then click OK.
  4. At the command prompt, type cd, and then press ENTER.
  5. At the command prompt, type the following command, and then press ENTER:

    msiexec /i “ ” TRANSFORMS=”C:SkipDotNetCheckVSTools.mst” INSTALLDIR=”” /qb+

    Note

  6. At the command prompt, type exit, and then press ENTER.

After you follow these steps, the Visual Studio Tools for Microsoft Dynamics GP 10.0 SDK is installed in the location that you specify in step 5. The default installation includes all the features of the Visual Studio Tools for Microsoft Dynamics GP 10.0 SDK.

You may want to install Visual Studio Tools SDK Service Pack 1 (SP1) while you install the Visual Studio Tools for Microsoft Dynamics GP 10.0 SDK. To do this by using a slipstream, type the following command in step 5:

msiexec /i “ ” TRANSFORMS=”C:SkipDotNetCheckVSTools.mst” PATCH=” ” INSTALLDIR=”” /qb+

Note In this command, is a placeholder for the path of the VSToolsSDK-KB945414-v10-ENU.msp file.

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 Dynamics GP 10.0 Service Pack 2.
When you use the methods in the “Workaround” section, make sure that you type the commands correctly. If you add a space or if you omit a space, you may receive the following error message:

This installation does not have a native user interface.

Article ID: 952376 – Last Review: September 26, 2012 – Revision: 5.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Dexterity
  • Developer Toolkit for Microsoft Dynamics GP
  • Visual Studio Tools for Microsoft Dynamics GP Software Development Kit
kbbug kbexpertiseadvanced kberrmsg kbtshoot kbmbsmigrate kbprb KB952376

See original article:
Error message when you try to install Dexterity or the Visual Studio Tools for Microsoft Dynamics GP 10.0 SDK: ".NET Framework 2.0 is not detected. Fatal error during installation"

The U.S. Payroll Tax Update stops responding when you run the payroll tax update on a 64-bit operating system in Microsoft Dynamics GP

When you run the U.S. Payroll Tax Update for Microsoft Dynamics GP on a 64-bit operating system, the payroll tax update stops responding.
This problem occurs because the automatic payroll tax engine is incompatible with 64-bit operating systems.
To resolve this problem, obtain the latest service pack for Microsoft Dynamics GP 10.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

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 Dynamics GP 10.0 Service Pack 3.

Article ID: 947191 – Last Review: September 26, 2012 – Revision: 6.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Payroll – U.S.
kbbug kbmbspayrolltaxupdate kbexpertiseadvanced kbtshoot kbmbsmigrate kbexpertiseinter KB947191

Read More:
The U.S. Payroll Tax Update stops responding when you run the payroll tax update on a 64-bit operating system in Microsoft Dynamics GP

Page 323 of 752« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories