Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you run an integration in Integration Manager for Microsoft Dynamics GP: “could not set foreground locking value to 0”.


View products that this article applies to.

Symptoms

When running an Integration in Integration Manager for Microsoft Dynamics GP, you receive the following error message:
could not set foreground locking value to 0

↑ Back to the top


Resolution

To resolve this problem, use the appropriate resolution.

Resolution 1
 
To resolve this problem, obtain the latest update for Integration Manager. Follow the instructions that are in the Readme.txt file that is included in the update. To obtain the update, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Integration Manager for Microsoft Dynamics GP 2010

Partners & Customers

https://mbs.microsoft.com/customersource/support/downloads/servicepacks/mdgp2010_integrationmanager.htm?printpage=false

Integration Manager for Microsoft Dynamics GP 10.0

PartnerSource

https://mbs.microsoft.com/partnersource/downloads/releases/integration_manager_10_downloads_for_microsoftdynamics10.htm?printpage=false


Customer Source

https://mbs.microsoft.com/customersource/support/downloads/servicepacks/integration_manager_10_downloads_for_microsoftdynamics10.htm?printpage=false

Resolution 2

Add a setting to the appropriate file that ignores foreground locking time-out errors. To do this, use the appropriate method:

Method 1 If you are using IntegrationManager.exe to run the integration, edit the Edit the Microsoft.Dynamics.GP.IntegrationManager.ini file to include the following settings:

[IMGPPrv]
ForegroundAlert=False
IgnoreLockError=True
HideMsgBox=True


Save the Microsoft.Dynamics.GP.IntegrationManager.ini file and restart Integration Manager.

Method 2 If you are using the Microsoft.Dynamics.GP.IntegrationManager.IMRun.exe file to run the integration, edit the IntegrationManager.IMRun.ini file.

If the IntegrationManager.IMRun.ini file does not does not exist, make a copy of the Microsoft.Dynamics.GP.IntegrationManager.ini file and rename it to Microsoft.Dynamics.GP.IntegrationManager.IMRun.ini. Save the Microsoft.Dynamics.GP.IntegrationManager.IMRun.ini file to the Integration Manager folder that contains the Microsoft.Dynamics.GP.IntegrationManager.exe file.


Verify the following settings:

[IMGPPrv]
ForegroundAlert=False
IgnoreLockError=True
HideMsgBox=True


Save the Microsoft.Dynamics.GP.IntegrationManager.IMRun.ini file and restart Integration Manager.






↑ Back to the top


Keywords: kbexpertiseadvanced, kberrmsg, kbmbspartner, kbexpertisebeginner, kbtshoot, kbmbsmigrate, kbbug, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 939045
Revision : 1
Created on : 1/7/2017
Published on : 1/23/2013
Exists online : False
Views : 175