Potential fatal error in LANSA Composer 4.0 when running Initialization
|Date:||1 March 2012|
|Product/Release:||LANSA Composer 4.0|
|Abstract:||Fatal error when attempting to create directory C:\Windows\TEMP\lobuser|
|Submitted By:||LANSA Technical Support|
In the LANSA Composer 4.0 client, a fatal error similar to the following is shown while importing supplied Transformation Maps using the Server Initialization Wizard when the LANSA Composer server is running on Windows.
The file x_err.log on the Windows server (typically in the C:\Windows\Temp folder) will contain an error similar to:
Wed Feb 29 08:58:16 2012
Release 12.0.0 Build 4042 Windows 2000/XP
Process : *SSERVER
Function : *SSERVE
Statement : 0
Message : (0480) - Fatal error when attempting to create directory C:\Windows\TEMP\lobuser.
Routine : X_Receive_Files
Job Number: 002340 OS User : PCXUSER
DBII=LC402GA2 GUSR=QOTHPRDOWN CMTH=C CDLL=LCOMGR32.DLL PROC=*SSERVER MODE=B PART=LIC LANG=ENG DEVE=N DATF=YMD DATS=Y USER=LICPGMLIB DBUG=N DBUS=LICPGMLIB DBIT=MSSQLS DBUT=MSSQLS DBCC=1 DBCT=3 PRTR=LPT1 HSKC=N ODBI=0 ITHP=N
ROOT=C:\PROGRAM FILES\LC402GA2 SERVER\X_WIN95
This error can occur if the user used to login to LANSA Composer does not have required authorities to the C:\Windows\Temp folder on the Windows server. The LANSA Composer server attempts to use subfolders in C:\Windows\Temp to receive BLOB data from the LANSA Composer client while importing supplied Transformation Maps during the Server Initialization.
To correct this error, ensure that the user used to login to LANSA Composer (for example PCXUSER) has the necessary authorities to the C:\Windows\Temp folder on the Windows server.
Note: Related errors may occur in other parts of the LANSA Composer client that attempt to exchange BLOB data with the Windows server, for example, Transformation Map prepare ands check operations and attachments handling, including import and export operations involving definitions that have attachments. In these other cases a different client-side error may be seen, but the server-side x_err.log will report a similar condition to that shown above.