| Trouble | Possible cause | Time of occurrence | Countermeasures |
|---|---|---|---|
| Installation unsuccessful (The value of the property 'type' cannot be parsed / VSTOInstaller.exe.config ) | A common installation problem experienced by almost all Microsoft Office add-on developers is that installation fails due to a long known Microsoft bug. | Error during installation (message box window). | 1. Find the file "VSTOInstaller.exe.config" in your "Program Files\..." folder and rename it for the time of EasyInput installation. 3. If problem persists, please create support ticket or contact EasyInput team at EasyInput@all-for-one.com describing the problem and giving the EI version number. |
| Transaction recording (SHDB or embedded recorder) stops or hangs incorrectly | SAP GUI software problem. Especcially with newer SAP NetWeaver version. | During transaction recording (Batch Input/ eCAT) via SHDB or embedded recorder. | Please upgrade your SAP GUI application (newest version or newest patch to the newest version, e.g. patch 8 to SAP GUI 7.40). |
| Installation unsuccessful (no EasyInput ribbon menu or error during installtion e.g. Compile error in hidden module: EasyInp10_X) | Unsupported platform (OS System, MS Excel, SAP GUI) or lack of administration rights during installation. | Error during installation or after installation when trying to open an EasyInput workbook. | 1. Check if your workstation IT platform is supported in User Installation Manual. Update you OS system, MS Excel or SAP GUI version if applicable. 2. Reinstall EasyInput - uninstall the solution (if found in Control Panel > Programs & Features) and install the EI once more(Setup.exe). 3. If problem persists, please create support ticket or contact EasyInput team at EasyInput@all-for-one.com describing the problem and giving the EI version number. |
| Connection to SAP system unsuccessfull (communication errors e.g. RFC communication failure: Error in network and communication layer: Partner NNN.NNN.NNN.NNN:33XX not reached: connection timed out) | Problem with tcp/ip connection on RFC port 33XX, where XX is the SAP system number | Error during any EasyInput action requiring connection to the SAP system. | 1. Check if port 33XX is open for communication with the SAP administrators (possible blocking by firewall, as SAP GUI uses normally 32XX port). 2. Check with the SAP administrators, whether the gateway service sapgwXX 33XX/tcp is set in the dispatcher file sapdpXX (where XX is the SAP system number) |
| RFC runtime failure popup windows appear. No RFC authorization for function module RFCPING. | Problem with RFC authorizations of the logged user. | Error during any EasyInput action requiring connection to the SAP system. | Add the necessary authorizations according to the user's or administrator's manual |
| EasyInput ribbon menu does not work/ is not refreshed. | EasyInput ribbon menu selected when Excel in "Edit mode" or other small program refresh problem. | EasyInput usage. | 1. Go out of the "Edit mode" (e.g. click once on another cell, or presc ESC on the keyboard). 2. Select another worksheet (by clicking on another worksheet tab). This should refresh EasyInput ribbon menu. |
| EasyInput script does not work as expected. Often error message 00 344 No batch input data for screen X Y appears. | EasyInput script not working on the given system or developed with errors. | Script execution. | 1. Switch on debug mode on the EI_Config worksheet (either for TR settings or for FM settings) 2. Re-run the script in debug mode. 3. Analyze: - each screen for the transaction script - EI_Debug worksheet both for TR and FM scripts 4. Check all the configuration options. 5. If nothing helps try re-creating the script fom the scratch. 6. For support users, please create support ticket if problem persists. |
| Error [E] Formatting error in the field XXXXX. [E] Input must be in the format __,___,___,___~.__V | Different decimal separator settings on the SAP and MS Excel side. | Error during EasyInput script run. | Allign your decimal separator settings between SAP and MS Excel either on the SAP side (System > User Profile > Own Data > Defaults > Decimal Notation) or on the MS Excel side (Settings > Advanced Settings > Switch off the use system decimal separators and enter new values). Do not use thousands separators on the Excel side. |
| Error RFC conversion failure, Error while converting a parameter to the correct data type... occurs while logging to SAP | Characters that are outside of SAP default (1100) codepage used in login or password. | Error during EasyInput script or using functions that require SAP connection. | On the EI_Logon worksheet enter the language/ codepage settings according to topic https://addons.all-for-one.pl/viewtopic ... 119&sid=07. |
| Various strange EasyInput behaviours when two or more EasyInput workbooks opened at the same time. | Switching between EasyInput workbooks during EasyInput process execution conflicts the EI logic. | Switching between EasyInput scripts while EasyInput macro runs. | Please close one of the EasyInput workbook or at least do not switch between EI workbooks while EI task is running. |
| Automation error message windows appear and Excel stops working. | Incorrect Excel/ EasyInput installation (incorrect VBA references) | Any EasyInput action. | Please try to uninstall EasyInput and install it again. Please check the references in the VBA editor (activate developper ribbon tab, open visual basic for applications window, select Tools > References from the menu, check the existing references, select the checkbox for CCO library). If nothing helps please create support ticket or contact the EasyInput team at EasyInput@all-for-one.com describing the problem (the EI version number, problem description, how to replicate the problem and the EasyInput workbook as attachment if possible). |
| EasyInput does not ask for password and reports error connected to username/ password. | There exist entry in SNC connection area. | Testing connection or running the script on a specific workbook. | Please check the EI_Logon worksheet in SNC connection area. If any entries exists there and SNC connection should not be used, then clear the entries and test connection. |
| Other unspecific error in the EasyInput Code (e.g. Unnknow application error :) | Unhandled error in the script/ configuration or in EasyInput code. | Any EasyInput action. | Please allow automatic sending of error information when proposed. Please create support ticket or contact the EasyInput team at EasyInput@all-for-one.com describing the problem (the EI version number, problem description, how to replicate the problem and the EasyInput workbook as attachment if possible). |