Error 2343 - specified path is empty is the one you need to look for.

And lo and behold, just above the error message, what do we find....

Action start 11:36:27: WriteIniValues.
WriteIniValues: File: Writing INI file values...
Section:
Key: , Value:
MSI (s) (28:C4) [11:36:27:876]: Note: 1: 2343
DEBUG: Error 2343:  Specified path is empty.

Looks like you are trying and failing to write an INI file.  Either you have something badly wrong in your INIFileTable, or you are trying to write the INI file to a non-existent folder. The INI file APIs do not create any folders if they are missing, so trying to write an INI file to a folder that does not exist is always going to fail.
If your INI file folder has no other files in it, then you need to use an explicit CreateFolder action to create the target folder. Or you need to install an "empty" INI file using the file table, as this will create any required folder automatically. Since the action that writes to INI files is sequenced after the action that installs files, installing a blank file will ensure that a target for write ini always exists. The other benefit of this approach is that you can apply LockPermissions to the INI file if it needs to have read write permissions but is going into the application folders or anywhere where a standard user has read access only.

...you can ignore icon/dialog control errors. Every MSI you look at will have at least one. In the top ten of such errors must be that which occurs in InstallShield-authored MSI where the horizontal rule which accompanies the 'InstallShield Wizard' text is 2 or 3 pixels wider than the dialog containing it. Sloppy but easy to shrug your shoulders at. Only R E A L L Y anal clients care (and yes, I *did* work for one!)

No, I am suggesting you investigate your project file to determine whether an INI file is part of the installation, and if so, check where it is being created.

Hi Ed,

Yes, there are some INI files being part of the installation and they are being created on c:\saplink 12_5---->1 file
c:\saplink 12_5\exe\3 files
c:\sybase12.5\ini\1file

Do I recall that SAP's INI files aren't in standard INI format? Wise deals with any file with an INI extension as being properly formatted and is too stupid to check. If I'm right, you'll need to remove the INIFile table entries and treat the INIs as normal files. That presents a problem if you need to configure them as they're installed: you may need to resort to a string-parsing script to handle that.

Deleting or removing entries from the INIFile table is causing all kind of errors in the File table as you stated above these files are part of the installation

Go back to your back-up (you *do* have Wise set up to save back-ups, right?) and use the 'INI Files' link in 'Installation Expert' view to delete the INI stuff. Make a note of the INI name first, then add each INI as a normal file.