Internal Error 2343

[eclayp]

I am using AdminStudio 3.5w/vp2.

I am trying to repackage WorkingModel2D 5.0. Everthing seems to complie fine from the Legacy Conversion Wizard. However, when I try to run the newly created msi, I get internal error 2343. I cannot find anything in the KB to give me a clue on where to look to recitfy this issue. Any assistance would be appreciated.

Thanks,
-Eric

P.S. Here is the log output from the Legacy Conversion Wizard:


Tuesday, January 07, 2003 08:02PM
Converting: C:\Packages\WorkingModel.inc to:

C:\Packages\WorkingModel.ism
Starting conversion
Creating project file
Reading repackager output file
Loading registry entries
Creating components for the files captured
Mapping registry information to the Advertising tables
Mapping typelib data from registry information to the TypeLib table
Mapping COM data from registry information
Mapping Application IDs from registry information and writing to the AppId table
Mapping ProgIDs from registry information
Writing to the Class table
Mapping file extensions and MIME types from registry information to the Extension and Mime

tables
Mapping shell extension verbs from registry information to the Verb table
*** Warning: Undefined shell verb 'open' (for ProgID 'WM.Document'): no defined file

extension could be found. This may result in ICE33 warnings.
*** Warning: Undefined shell verb 'print' (for ProgID 'WM.Document'): no defined file

extension could be found. This may result in ICE33 warnings.
*** Warning: Undefined shell verb 'printto' (for ProgID 'WM.Document'): no defined file

extension could be found. This may result in ICE33 warnings.
Writing to the ProgId table
*** Warning: Undefined default icon for ProgId 'WM.Document': at least one shell

extension verb for the ProgId is required. This may result in ICE33 warnings.
Mapping NT services from registry information to the ServiceInstall and ServiceControl

tables
Mapping application paths from registry information
*** Warning: Registry entry for AppPath for 'Ip.exe' will remain in the Registry table

because '%ProgramFilesFolder%\Working Model 2D\PROGRAM\ip.exe' is not a known file.
Mapping environment variables from registry information to the Environment table
Processing .INI file changes and writing to the IniFile table
Scanning for ODBC drivers and writing to the ODBCSource and ODBCDriver tables
Applying merge modules
Creating directory folders and writing to the CreateFolders table
Writing unmapped registry information to the Registry table
Creating shortcuts and writing to the Shortcut table
Building .msi package
Created release folders
AdminExecuteSequence table successfully built
AdminUISequence table successfully built
AdvtExecuteSequence table successfully built
AdvtUISequence table successfully built
InstallExecuteSequence table successfully built
InstallUISequence table successfully built
Directory table successfully built
Feature table successfully built
FeatureComponents table successfully built
Component table successfully built
Loading File table
Building File table
File table successfully built
Building MsiFileHash table
MsiFileHash table successfully built
Class table successfully built
Extension table successfully built
ODBCDataSource table successfully built
ODBCDriver table successfully built
ActionText table successfully built
AppSearch table successfully built
BindImage table successfully built
CCPSearch table successfully built
Condition table successfully built
AppId table successfully built
Property table successfully built
BBControl table successfully built
Billboard table successfully built
Binary table successfully built
CompLocator table successfully built
Complus table successfully built
ControlCondition table successfully built
ControlEvent table successfully built
CreateFolder table successfully built
CustomAction table successfully built
Error table successfully built
DrLocator table successfully built
DuplicateFile table successfully built
Environment table successfully built
EventMapping table successfully built
FileSFPCatalog table successfully built
Font table successfully built
IniFile table successfully built
IniLocator table successfully built
IsolatedComponent table successfully built
LaunchCondition table successfully built
LockPermissions table successfully built
MIME table successfully built
MoveFile table successfully built
MsiAssembly table successfully built
MsiAssemblyName table successfully built
MsiDigitalCertificate table successfully built
MsiDigitalSignature table successfully built
ODBCAttribute table successfully built
ODBCSourceAttribute table successfully built
ODBCTranslator table successfully built
PatchPackage table successfully built
ProgId table successfully built
PublishComponent table successfully built
Registry table successfully built
RegLocator table successfully built
RemoveFile table successfully built
RemoveIniFile table successfully built
RemoveRegistry table successfully built
ReserveCost table successfully built
SelfReg table successfully built
ServiceControl table successfully built
ServiceInstall table successfully built
SFPCatalog table successfully built
Shortcut table successfully built
Signature table successfully built
TextStyle table successfully built
TypeLib table successfully built
UIText table successfully built
Upgrade table successfully built
Verb table successfully built
_Validation table successfully built
Searching project for extract-at-build components...
Validating Custom Action sequencing
Dialog AdminChangeFolder for language English (United States) built
Dialog AdminNetworkLocation for language English (United States) built
Dialog AdminWelcome for language English (United States) built
Dialog CancelSetup for language English (United States) built
Dialog CustomSetup for language English (United States) built
Dialog CustomSetupTips for language English (United States) built
Dialog CustomerInformation for language English (United States) built
Dialog DatabaseFolder for language English (United States) built
Dialog DestinationFolder for language English (United States) built
Dialog DiskSpaceRequirements for language English (United States) built
Dialog FilesInUse for language English (United States) built
Dialog InstallChangeFolder for language English (United States) built
Dialog InstallWelcome for language English (United States) built
Dialog LicenseAgreement for language English (United States) built
Dialog MaintenanceType for language English (United States) built
Dialog MaintenanceWelcome for language English (United States) built
Dialog OutOfSpace for language English (United States) built
Dialog PatchWelcome for language English (United States) built
Dialog ReadyToInstall for language English (United States) built
Dialog ReadyToRemove for language English (United States) built
Dialog SetupCompleteError for language English (United States) built
Dialog SetupCompleteSuccess for language English (United States) built
Dialog SetupError for language English (United States) built
Dialog SetupInitialization for language English (United States) built
Dialog SetupInterrupted for language English (United States) built
Dialog SetupProgress for language English (United States) built
Dialog SetupResume for language English (United States) built
Dialog SetupType for language English (United States) built
Dialog SplashBitmap for language English (United States) built
Resolving strings...
Language English (United States) built
Files built
Media table successfully built
Performing Upgrading and Patching Validation
Product1\Release1 - 0 error(s), 0 warning(s)
Finished successfully.

[dynamox]

Hello. Did a search on your error and found a link to msdn site. The error code stands for "Specified path is empty". Also Microsoft's KB has a reference about this error, when installing office and Lotus Notus on the same computer, i don't know if this is the case with you. Second link i found very helpfull in everyday repackaging life.



http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/windows_installer_error_messages.asp

and

http://isg.ee.ethz.ch/tools/realmen/det/msi.en.html

[eclayp]

Thanks. Didn't even occur to me to look in MSDN. While I now know what the error means, now I need to figure out what specified path is missing. Time to start digging again.

[TsungH]

Run Full MSI Validation Suite on your package, and see if there is any error.

[eclayp]

That got me where I needed to go. Thank you!

[CChong]

Have you found any luck or solutions for this error, Eric? I got the same problem. I already tried to add a DATABASEDIR row in the Directory table as the Q108093 article suggests, but it still doesn't work. Thank you.