File not found: VBA6.dll error occurs or GP crashes

Beth Gardner - Click for blog homepageThis is a follow up to my previous post on the VBA6.dll not found error (for 64-bit). I have found this can occur on 32-bit computers and Microsoft Dynamics GP 10.0 and GP 2010.

Important: This post contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base (KB) Article:

I have found that the issue is because the 4.0 registry key is missing.  This is created with earlier versions of Microsoft Office and Microsoft Dynamics GP.

To resolve this error, you need to add the 4.0 registry key. 

Here are the steps:

  1. Make a full backup of the system registry.
     
  2. Export all modifications to a .package file from Microsoft Dynamics GP under Tools | Customize | Customization Maintenance.
     
  3. Create a .reg file that contained the following in Notepad:
     
    Windows Registry Editor Version 5.00
     
    HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.0
     
    @=”Visual Basic For Applications”
     
    HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.09 
     
    HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.09win32 
     
    @=”C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL”
     
    HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.0FLAGS 
     
    @=”0″
     
    HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.0HELPDIR 
     
    @=”C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\”
     
  4. Next, double-clicked the .reg file, so it was added to the system registry. 
     
  5. The HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.1 key should point to the VBE7.dll file.
     
  6. Next delete the .vba files that were 4kb and renamed the .vba files that were over 4kb in the Microsoft Dynamics GP code folder.
     
  7. Start Microsoft Dynamics GP.  You should not receive any errors.
     
  8. Import the .package file.  Verify the code works and the error no longer occurs.

I have had a few customers state that they had to unregister the msvbvm60.dll.  But I did not run across that with the customers I have streamed in with.

Beth Gardner

Support Escalation Engineer
Microsoft Dynamics GP Developer Support

16-Nov-2010: Added link to previous article.

Read more:
File not found: VBA6.dll error occurs or GP crashes

November 15, 2010 · David Musgrave · 2 Comments
Tags: , , , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 2,496

Solution to "File not found: VBA6.DLL" Error Message

The File Not Found: VBA6.DLL issue which I had explained in my previous post has got a solution.

Thanks to Japheth Nolt, who pointed me to this Partner Forum post.

The following are the steps to fix this issue, taken directly from Dynamics GP Partner Forum Post (Link To the Original Post: File Not Found: VBA6.dll):

———-
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 

1. Export all customizations to a .package file.

2. Close Microsoft Dynamics GP.

3. Make a backup of the system registry.

4. Change the following key in the system registry:

KEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.09win32

to have the path of this: C:Program FilesCommon Filesmicrosoft sharedVBAVBA6VBE6.dll

Note, if on a Windows 2008 Server R2 install the key was this: HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.19win32

5. Delete all VBA files with a file size of 4KB.

6. Rename all VBA files with a file size greater than 4KB.

7. Start GP.

8. Open VBA editor.

9. Check the VBA reference to ensure the path is to the C:Program FilesCommon Filesmicrosoft sharedVBAVBA6VBE6.dll file.

10. Add a window and field to VBA and test the message box code.

11. Verify the message box works.

12. Import all customizations.

13. Verify more than one customization works.

Note, this has only been tested on an Office 32-bit installation. If you have an Office 64-bit installation, you will need to uninstall it and then install the 32-bit version. This will not affect Outlook user profiles.
———-

What I did is the following:

1. I removed all the VBA files from GP Folder in my 32 Bit machine.

2. I performed the steps listed above from #1 to #4 (modifying the registry entry).

3. I launched GP and opened the VBA Editor, to make sure that the Visual Basic for Applications Reference is pointing to the path C:Program FilesCommon Filesmicrosoft sharedVBAVBA6VBE6.DLL.

4. Closed GP. Relaunched it.

5. Imported the VBA Customizations that were exported from 64 Bit machine.

6. My customizations started working.

IMPORTANT NOTE: You must re-reference any 3rd Party plugin references after importing the VBA Packages, in case these 3rd Party plugins sit in Program Files (x86) folder in 64 Bit machine.

Hope this is helpful for people who face this issue.

VAIDY

Read more:
Solution to "File not found: VBA6.DLL" Error Message

August 24, 2010 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 907

Remove Dynamics GP Web Service

Steps to remove Microsoft Dynamics GP Web Services



1. Remove “Adam Instance DynamicsSecurityService” in AddRemove Programs.


2. In IIS Manager, delete “Dynamics Security Admin Service” Web site.


3. In IIS Manager, delete “DynamicsGPWebServices” and DynamicsSecurityService” virtual directories from the Web site that the Web Services for Microsoft Dynamics GP was installed on.


4. In IIS Manager, delete the “DynamicsSecurityAdminServiceAppPool”, DynamicsSecurityServiceAppPool”, and “GPWebServicesAppPool” application pools.


5. Delete the “Microsoft Dynamics” folder from C:Program FilesCommon FilesMicrosoft Shared.


6. Delete “GPWebServices” folder from C:Program FilesMicrosoft Dynamics (This is the default location for Web site files.).


7. Delete “Dynamics GP Web Service Exception Management Console” and “Dynamics Security Console” shortcuts from Administrative Tools program folder.


8. Delete related Registry Keys for Web Services for Microsoft Dynamics GP 9.0.


9. Remove the DynamicsGPWebServices key under HKEY_LOCAL_MACHINESOFTWAREMicrosoft

Run following SQL Script to remove SQL Objects from DYNAMICS as well as Company Database.

Against DYNAMICS DB :

drop view ReqCurrency
drop view ReqCurrencyAccess
drop table WSErrorProperties
drop table WSExceptionLog
drop table WSInstallStatus
drop table WSInstallSteps
drop procedure ws_delete_WSExceptionLog
drop procedure ws_deleteall_WSExceptionLog
drop procedure ws_get_MC40200
drop procedure ws_get_SY01500
drop procedure ws_get_WSErrorProperties
drop procedure ws_get_WSExceptionLog
drop procedure ws_get_WSExceptionLog_Summary
drop procedure ws_get_WSExceptionLog_ValidationException
drop procedure ws_get_WSInstallStatus
drop procedure ws_getall_WSInstallStatus
drop procedure ws_insert_WSExceptionLog
delete eConnect_Out_Setup where DOCTYPE in(‘WSCompany’, ‘WSCurrency’, ‘WSCurrencyAccess’)

Run following sql script against all Company Database

drop view ReqCurrencyPostingAccountView
drop view ReqGLAcct
drop view ReqGLFixedAllocAcct
drop view ReqGLFixedAllocDistAcct
drop view ReqGLHeaderView
drop view ReqGLLineView
drop view ReqGLPostingAcct
drop view ReqGLPostingAcctCurrencies
drop view ReqGLUnitAcct
drop view ReqGLVarAllocAcct
drop view ReqGLVarAllocDistAcct
drop view ReqGLVarAllocDistBreakAcct
drop view ReqIVFee
drop view ReqIVHeaderView
drop view ReqIVItemCurrency
drop view ReqIVItemHeader
drop view ReqIVItemQuantity
drop view ReqIVItemQuantityBinDetail
drop view ReqIVItemVendor
drop view ReqIVItemWarehouse
drop view ReqIVKit
drop view ReqIVKitComponent
drop view ReqIVLineBinDetailView
drop view ReqIVLineLotDetailView
drop view ReqIVLineSerialDetailView
drop view ReqIVLineView
drop view ReqIVPricing
drop view ReqIVPricingDetail
drop view ReqIVSalesItem
drop view ReqIVService
drop view ReqPAAccounts
drop view ReqPAChangeOrderHeader
drop view ReqPAContractHeader
drop view ReqPAEmpExpDist
drop view ReqPAEmpExpHeader
drop view ReqPAEmpExpLine
drop view ReqPAEmpExpLineTax
drop view ReqPAMiscLog
drop view ReqPAMiscLogDist
drop view ReqPAMiscLogLines
drop view ReqPAProjectBudgetHeader
drop view ReqPAProjectHeader
drop view ReqPATimesheetDist
drop view ReqPATimesheetHeader
drop view ReqPATimesheetLine
drop view ReqPaymentCard
drop view ReqPMHeaderDistView
drop view ReqPMHeaderTaxView
drop view ReqPMHeaderView
drop view ReqPMVendor
drop view ReqPMVendorInetAddress
drop view ReqPMVendorPAOptions
drop view ReqPOHeaderFreightTaxView
drop view ReqPOHeaderMiscTaxView
drop view ReqPOHeaderTaxView
drop view ReqPOHeaderView
drop view ReqPOLineTaxView
drop view ReqPOLineView
drop view ReqPurInvDistView
drop view ReqPurInvHeaderFreightTaxView
drop view ReqPurInvHeaderMiscTaxView
drop view ReqPurInvHeaderTaxView
drop view ReqPurInvHeaderView
drop view ReqPurInvLineApplyRecptView
drop view ReqPurInvLineTaxView
drop view ReqPurInvLineView
drop view ReqPurRecptDist
drop view ReqPurRecptHeader
drop view ReqPurRecptLine
drop view ReqPurRecptLineBin
drop view ReqPurRecptLineLotNum
drop view ReqPurRecptLineSerNum
drop view ReqRecvDocComm
drop view ReqRecvDocDist
drop view ReqRecvDocHeader
drop view ReqRecvDocTax
drop view ReqRMCashReceiptDist
drop view ReqRMCashReceiptHeader
drop view ReqRMCorporateAccount
drop view ReqRMCustomer
drop view ReqRMCustomerAddress
drop view ReqRMCustomerInetAddress
drop view ReqRMSalesPersonCommisionsView
drop view ReqRMSalespersonInetAddress
drop view ReqSODistributionView
drop view ReqSOHeaderFreightTaxView
drop view ReqSOHeaderMiscTaxView
drop view ReqSOHeaderTaxView
drop view ReqSOHeaderView
drop view ReqSOLineComponentView
drop view ReqSOLineTaxView
drop view ReqSOLineView
drop view ReqSOLotDetailView
drop view ReqSOSerialDetailView
drop table WSPolicyBehaviorSelectionParameter
drop table WSPolicyBehaviorSelection
drop table WSPolicyBehavior
drop table WSPolicy
drop table WSParameter
drop table WSBehaviorOption
drop table WSBehavior
drop procedure ws_delete_WSBehavior
drop procedure ws_delete_WSBehaviorOption
drop procedure ws_delete_WSParameter
drop procedure ws_delete_WSPolicy
drop procedure ws_delete_WSPolicyBehavior
drop procedure ws_delete_WSPolicyBehaviorSelection
drop procedure ws_delete_WSPolicyBehaviorSelectionParameter
drop procedure ws_get_Behavior
drop procedure ws_get_MC40000
drop procedure ws_get_Policy
drop procedure ws_get_PolicyByOperation
drop procedure ws_get_PolicyNoDefaulting
drop procedure ws_get_SY00300
drop procedure ws_insert_WSBehavior
drop procedure ws_insert_WSBehaviorOption
drop procedure ws_insert_WSParameter
drop procedure ws_insert_WSPolicy
drop procedure ws_insert_WSPolicyBehavior
drop procedure ws_insert_WSPolicyBehaviorSelection
drop procedure ws_insert_WSPolicyBehaviorSelectionParameter
drop procedure ws_update_WSPolicyBehaviorSelection
drop procedure ws_update_WSPolicyBehaviorSelectionParameter
delete eConnect_Out_Setup where DOCTYPE = ‘WSBank’
delete eConnect_Out_Setup where DOCTYPE = ‘WSCashReceipt’
delete eConnect_Out_Setup where DOCTYPE = ‘WSCompanyAddress’
delete eConnect_Out_Setup where DOCTYPE = ‘WSCorporateAccount’
delete eConnect_Out_Setup where DOCTYPE = ‘WSCountryRegionCode’
delete eConnect_Out_Setup where DOCTYPE = ‘WSCurrencyPostingAccount’
delete eConnect_Out_Setup where DOCTYPE = ‘WSCustomer’
delete eConnect_Out_Setup where DOCTYPE = ‘WSCustomerAddress’
delete eConnect_Out_Setup where DOCTYPE = ‘WSFee’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLAccount’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLAccountCategory’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLAccountFormat’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLFixedAllocationAccount’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLPostingAccount’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLTransaction’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLUnitAccount’
delete eConnect_Out_Setup where DOCTYPE = ‘WSGLVariableAllocationAccount’
delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoriedItem’
delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoryAdjustment’
delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoryTransfer’
delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoryVariance’
delete eConnect_Out_Setup where DOCTYPE = ‘WSItem’
delete eConnect_Out_Setup where DOCTYPE = ‘WSItemClass’
delete eConnect_Out_Setup where DOCTYPE = ‘WSItemCurrency’
delete eConnect_Out_Setup where DOCTYPE = ‘WSItemVendor’
delete eConnect_Out_Setup where DOCTYPE = ‘WSItemWarehouse’
delete eConnect_Out_Setup where DOCTYPE = ‘WSKit’
delete eConnect_Out_Setup where DOCTYPE = ‘WSMulticurrencySetup’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesCreditMemo’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesDocument’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesFinanceCharge’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesInvoice’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesMiscellaneousCharge’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesReturn’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPaymentCardType’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPaymentTerms’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPriceLevel’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPricing’
delete eConnect_Out_Setup where DOCTYPE = ‘WSProject’
delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectBudget’
delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectChangeOrder’
delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectContract’
delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectEmployeeExpense’
delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectMiscellaneousLog’
delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectTimesheet’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPurchaseInvoice’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPurchaseOrder’
delete eConnect_Out_Setup where DOCTYPE = ‘WSPurchaseReceipt’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesCreditMemo’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesDebitMemo’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesDocument’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesFinanceCharge’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesInvoice’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesReturn’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesServiceRepair’
delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesWarranty’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesBackorder’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesDocument’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesDocumentTypeSetup’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesFulfillmentOrder’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesInvoice’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesItem’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesOrder’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesperson’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalespersonCommissions’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesProcessHoldSetup’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesQuote’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesReturn’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesSetup’
delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesTerritory’
delete eConnect_Out_Setup where DOCTYPE = ‘WSService’
delete eConnect_Out_Setup where DOCTYPE = ‘WSShippingMethod’
delete eConnect_Out_Setup where DOCTYPE = ‘WSUofMSchedule’
delete eConnect_Out_Setup where DOCTYPE = ‘WSVendor’
delete eConnect_Out_Setup where DOCTYPE = ‘WSVendorAddress’
delete eConnect_Out_Setup where DOCTYPE = ‘WSWarehouse’



See original here:
Remove Dynamics GP Web Service

January 16, 2010 · Sandip Jadhav · No Comments
Tags: , , , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 582