Pem init error reading e3prot tmp inpa

UPDATE: FIRST TRY POST #2!!! After successfully installing INPA 3.01(installer 4.4.7)/Ediabas 6.4.3 on Windows 7(Ultimate, 32bit, English) running on a MacBook Air, I tried upgrading to INPA 5.02/Ediabas 6.4.7 but the 1st step of the upgrade install fails with a ‘clang’ and the following error messages:

«Setup was unable to create the directory «C:BMW ToolsenglishINPA_Engl_?ersetzung_PL2».

Error 123: The filename, directory name, or volume label syntax is incorrect.»

…(deleted previous ramblings of frustation)

Work around solution FOUND!

It turns out that that there is a folder named «INPA_Engl_�bersetzung_PL2» in the original installation package’s EC-APPS > INPA > english folder. The «�bersetzung»(‘translation’) was showing up as «?ersetzung»(‘replacing’ is not the intended term apparently) and causing the syntax error which resulted in the error message:

«Setup was unable to create the directory «C:BMW ToolsenglishINPA_Engl_?ersetzung_PL2».
Error 123: The filename, directory name, or volume label syntax is incorrect.»

Because I am running Windows 7 Ultimate, which can run on all languages, I switched to German as the main language for the OS. This allowed me to see the small, initial language selection window(in Windows setting, before entering the INPA setting) for the first time! I initially selected English for the installation language(in the initial Windows setting install lanaguage selection, before entering the INPA setting), but this resulted in the same syntax error (note: the OS language was set to German, so the OS being set to German was not a cure all). Because the initial syntax error corrupted the existing INPA 3.01 installation, I deleted all the INPA/Ediabas/BMW Tools files, and reinstalled from INPA 3.01, this time selecting German as the install language(in the initial, small language selection window of Windows setting, not the INPA setting). This resolved the syntax error!!! :lol (weekend geekdom prevailed!)
The installation began to proceed in the INPA interface, and from there(now within the INPA setting) I selected English as the language and further selected the UK rectification configurations and it did not cause any issues(note: the OS is still in German). After the installation finished, INPA 5.02 opened within German and English OS (although with some PEM-init errors below).

PEM-init:
error reading DMF files:
File..prtenglishE3PROTOK.DMF not found

PEM-init:
error reading DMF files:
File..prtenglishE3ETIKET.DMF not found

PEM-init:
error reading DMF files:
File %s not found.

I looked up the DMF files in the INPA User Documentation v.2.2(20.07.2000), and it turns out that the two DMF files(E3PROTOK.DMF and E3ETIKET.DMF) are originally in the stallation package files under EC-APPS > INPA > PRT in the following folders(all of which had the same two files each):

ENGLISCH
ENGLISCH.MET
ENGLISH
ENGLISH.MET

I copied & pasted these folders into the C: drive’s EC-APPS > INPA > PRT folder then opened INPA. The PEM-init errors are gone! :lol

I’m sure there is a more enlightened method to resolve the syntax error, but not being a programmer, this is enough for me. I welcome a more astute explanation though.

I’m still getting acquainted with INPA without even having a K+D CAN cable for my 2007 320i(I hope the guidelines I’ve read were correct). Now I feel I can go ahead with a purchase so I can actually use INPA and move on to DIS 57!!! I’d like to register a new battery eventually(as soon as possible).

One indy told me that a new battery install (without continuous power to the ECU) would set off a ‘reset'(wipe out previously stored data about the battery) and essentially do the same thing as ‘registering’ a new battery through DIS, although the time, date, and steering angle would have to be reset manually. Supposedly a battery replacement ‘registration’ with continuos power provided during the battery replacement would not require the manual resets, for the memory would be intact during the process.
There are so many that say registration is a must(one spoke of an aftermarket battery exploding in his car’s trunk while driving because it was not registered and resulted in over charging?), and there are just as many that say that its a load of balogna(way for stealers to make some easy dough) that I have decided to go the safest route — check for myself if indeed a DIS battery registration actually does something more meaningful than a ‘reset’ caused by powering down(disconnecting the battery) to replace the battery.

Comments are very welcome.

In this article I will share solutions of BMW INPA Errors,belows list 12 errors of BMW INPA when installing BMW INPA Software.Hope it is helpful!

Error Message 0020: Incorrect or Missing Driver. The programme will be aborted!

Conditions:

You have access to  \smuc0900sg . You are linked to this drive and would like to start an INPA script.

Reason 1: Missing Ediabas.ini file in C:Winnt.

Reason 2: You are not connected to the controller.

For developers: Simulation is not switched on in the Ediabas.ini file.

Solution:  Copy the Ediabas.ini file from C:EdiabasBin to C:Winnt.

SYS-00002: ECU variation description file not found.

The error occurs when starting an INPA script.

Reason 1: The *.prg SGBD is not located in the path C:EdiabasEcu.

Solution 1: Copy the *.prg SGBD into the ECU directory.

Reason 2: The external table T_GRTB.prg doesn’t exist in the directory C:EDIABASECU

or it is obsolete.

Solution 2: Copy the file into the ECU directory or update the external table using the ECCO

Web Client.

INPA Error: Error at Compiling Abort!

The following error message appears when starting an INPA script.

Reason 1: An INPA script with the ending IPO was started by the programme INPA.EXE

instead of by the programme INPALOAD.EXE.

Solution 1: Only start INPA scripts that end with IPO with INPALOAD.EXE.

Reason 2: The selected INPA script doesn’t exist in the C:INPASGDAT directory.

Solution 2: Update the INPA scripts using the ECCO Web Client.

Reason 3: INPA Version 5.0.1: The INPA script *.IPO can’t be started with a double-click in

the directory C:INPASGDAT*.IPO.

Solution 3: Update to Version 5.0.2.

Reason 4: INPA Version 5.0.1: The desktop link of an INPA script doesn’t work.

Solution 4: The target path must be expanded to include the INPALOAD path. To do this,

click the desktop link once with the right mouse button and go to ‘Properties’.

Expand the target path to include C:INPABININPALOAD.exe for Windows NT

(see Fig.) and C:EC-AppsINPABININPALOAD.exe for Windows XP.

Reason 5:  The file startger.ipo of the german installation and the file startus.ipo of the

english installation don’t exist in the directory INPACFGDAT.

Solution 5: Install INPA once again.

IFH-0018: Inizialisation Error – INPA doesn’t work but Toolset yet

The error occurs if a SGBD is running by INPA or CASCADE. If the same SGBD is loaded in

the Toolset it will not occure an inizialisation error.

Reason 1: The communications port COM1 doesn’ exist, but COM3 yet. The Toolset is

working without the inizialisation error, because the file OBD.ini exists in the

directory C:Ediabasbin. But the file OBD.ini has to exist in the direcory

C:Windows.

Solution 1: Copy the file OBD.ini in the directory C:Windows or create a new one. (Creation

of OBD.ini q.v. 3.3).

Reason 2:  q.v. 3.3

Solution 2: q.v. 3.3

IFH-0027: IFH not found The Programm was aborted!

The error occurs when starting INPA.

Reason 1: The setting for the interface in the configuration file Ediabas.ini doesn’t exist.

Solution 1: Please do the settings for the interface e.g.:

Interface = STD:OBD

Reason 2: The setting for the interface in the configuration file Ediabas.ini is

Interface=STD:OMITEC, but the OMITEC driver isn’t installed correctly.

Solution 2: Install the OMITEC driver with the instructions

InstructionforOMITECInstallation.pdf via the GIS server.

Reason 3: The setting for the interface in the configuration file Ediabas.ini is

Interface=OMITEC, but the correct setting is Interface=STD:OMITEC.

Solution 3: Please do the settings for the interface Interface=STD:OMITEC.

Reason 4: The old OMITEC driver wasn’t uninstalled correctly.

Solution 4: Please uninstall the old OMITEC driver with the instructions

InstructionforOMITECInstallation.pdf via the GIS server.

INPA Error: Opening Inpa – Transmission error returned a_0x2

Reason:  During the installation of Ediabas/Inpa, the configuration “Without configuration”

was selected.

Solution:  When running the installation programme, select a configuration, e.g. “BMW

Plant 1.1 Munich”.

INPA Error: Only a white screen appears when you run INPALOAD.EXE.

Reason 1: The api.dll or api32.dll file has been manually copied into the WINDOWS

directory with Windows XP and into the WINNT directory with Windows NT.

Solution 1: Delete the file api.dll or alternatively api32.dll from the WINDOWS or alternatively

the WINNT directory. The file may only exist in the directory EDIBASBIN.

Reason 2: You have installed the 32-bit version of INPA (as of Version 5.0.1) and have not

performed an update of the INPA scripts.

Solution 2: Update the INPA scripts using the ECCO Web Client.

INPA Error: DTM is no longer supported

Reason:  This error message appears if INPA.INI has been copied from Version 4.7.7 to

Version 5.x.x.

Solution:  Since it can’t be excluded that even more files from the old version have been

mixed with the new ones, the old ones must be deleted, or alternatively

reinstalled (see Chapter 5). Reinstall INPA using the Global Information Service

(GIS) https://gis.bmw.com.

INPA Error: Bridge16.exe can’t be initialised

Reason 1:  A 16-bit INPA script has been started with the 32-bit version of INPA (as

of Version 5.0.1).

Solution 1:  Update the INPA scripts using the ECCO Web Client.

Solution 2:  Convert the INPA script to the standard ‘includes’ for the 32-bit version.

To do this, contact the respective person responsible for INPA at TI-43x

(see \smuc0900sgrefReferenzReferenz.inp)

Reason 2:  A 16-bit DLL has been found, which means the developer of the INPA

script is using a 16-bit DLL.

Solution 2: The developer of the INPA script must convert the DLL to 32-bit.

Error when opening the error file abort:

Reason:  This error occurs with Windows XP because the user doesn’t have the correct

rights to change files in the directory C:INPABin.

Solution: The user needs “Power user” rights or the user needs the appropriate write rights

to the “INPA” directory.

 Compiler: File: INPADEUTSCH***.OUT not found!

Reason:  The path C:EDIABASBIN has not been set in the ‘Path’ system variable.

Solution: Set the path C:EDIABASBIN in the ‘Path’ system variable. (q.v. chapter 2.1).

(Visited 500 times, 1 visits today)