Friday, July 13, 2012

System DSN is not appearing on the GP Login Window

Problem :
               If the created system DSN is not appearing on the GP Login Window, and if your operating system is 64-bit the problem is because of the 64-bit version of ODBC. Since GP is 32-bit, it cannot recognize the 64-bit system DSN created using 64-bit version ODBC.

Resolution :
                  Go to "C:\Windows\SysWOW64", find the "odbcad32.exe" and double click, and create the DSN as usual. Now the created DSN will appear on the GP Login Window.


Tuesday, October 4, 2011

econnect : (Exception from HRESULT: 0x8000401A)

Error Message (Great Plains or econnect 9/10):- The server process could not be started because the configured identity is incorrect, Check the username and password. (Exception from HRESULT: 0x8000401A).

Cause of Error:- This error occurs when the domain user password is changed after installing econnect 9/10. Because while installing econnect 9/10 it takes the domain user name and password for installation, and thus sets the username and password. When the domain password is changed after a while by the administrator for some security reasons, there after this error will appear hindering the econnect 9/10 service from working.

Resolution:-

Type "dcomcnfg" in the run window, which will open the Component Service window. Expand the tree to select the "COM+ Application" node in the left panel. Right click on the "econnect 9 for Great Plains" or "econnect 10 for Great Plains" icon on the right panel and click the "Properties" menu. Click the "Identity" tab, re-enter the "Password" and "Confirm password" with the current domain user password and click "Apply" button followed by "Ok" button.



Right click on the "econnect 9 for Great Plains" or "econnect 10 for Great Plains" icon on the right panel and click the "Start" menu.












Monday, August 25, 2008

How to create a chunk file ?

Open Dexterity Utilities and perform the following steps:

1) Open the source dictionary using the Development Dictionary (File -> Open Source Dictionary).
2) From the Toolbar, select Utilities -> Extract to extract all resources into an Extracted Dictionary.
3) If you do not have any alternate forms and/or reports, skip to step 7.
4) Open the destination dictionary using the Extracted Dictionary you created in step 2 (File -> Open Destination Dictionary).
5) From the Toolbar, use Transfer -> Dictionary Module to transfer any alternate forms and/or reports into the Extracted Dictionary.
6) Close the destination dictionary (File -> Close Destination Dictionary).
7) Close the source dictionary (File -> Close Source Dictionary).
8) Open the editable dictionary by using the Extracted Dictionary created in step 2 (File -> Open Editable Dictionary).
9) If you do not have any alternate forms and/or reports, skip to step 11.
10) From the Toolbar, go to Resources -> Series Resources. Check both the All Resource Types and All Series check boxes, and click Update.
11) From the Toolbar, select Utilities -> Product Information. Enter the Product Name, Product ID, the names of the custom forms and reports dictionaries, and the compatibility information. Then click OK. Make sure the Set file is DYNAMICS.SET and the Dictionary is set to 0.
12) Select Utilities -> Auto Chunk. Then use the Browse button to select the filename of the Chunk Dictionary; use an 8.3 format filename with the extension .cnk. Next select a module (I usually use 19, which was labeled as Dexterity in older versions), and enter your major, minor, and build numbers). Finally, select Total Compression to remove the source code from the final Chunk, and press OK.
13) Close the editable dictionary (File -> Close Editable Dictionary).