I have an application that was creating a cab and exe, however recently when I try to install, I get a fatal
error something like
unable to complete due to missing file
C:\Temp\msflqws.pdw\$(DLLSelfRegister.exe)
It sounds as though somewhere in the package the msflqws.pdw file is set to self-register (its unlikely this file can self-register). Maybe there is a checkbox to keep this from happening with this file (most install programs do).
Hope it helps, Rob
robschultz@yahoo.com
-Focus on the solution to the problem, not the obstacles in the way.-
msflqws.pdw is probably the temp directory designated in the setup.lst file. It looks like the setup.lst file is corrupt, as it is saying that $(DLLSelfRegister.exe) is a file when it was probably *supposed to be* some other "<file>.exe" set to $(DLLSelfRegister).
Go through the Package and Deployment again and make sure that all the files are good. Then after the .CAB is made, check out setup.lst and give it a once over to make sure that all the files are listed properly.
Hello there
I try to use to Package and delpoyment wizard for creating the installation CD for my application but hten when i do that i run through an error called ******.cab file cannot be created see if u have proper access to destination or disc not full.Can anyone please let me know how i can slove this?
I have created a package for my vb application using the PWD. It includes a third party activex dll provided by Scansoft and msXml20.dll. I have completed all the steps including creating a dependency file before creating the package. The problem is that whenever I try to instll the package Both the dlls fail to self register on the target machine when they should have. Is there anybody who can help.
I know the initial post of this problem was near on a year ago now, but if it still stands then it sounds like your problem is due to the Calendar control. Check out this URL that should solve it for you
I try to use to Package and delpoyment wizard for creating the installation CD for my application but when i do that i run through an error called "Run-Time Error- Class not registered. Who can help with?
i had created an .exe file for my vb project. its running in a machine which had vb application but in other system it finds error during the report display. its shows
run time error 713
application defined or object defined error
Mr. JPresley,
Till now if u haven't fixed ur problem for application deployment here is the solution, Probably u r using MSCAL.ocx in ur project.that has got an error for self registering. u need to modify ur *.lst file generated by setup.The change u need to make is
Open the Setup.lst file in a text editor, such as Notepad. Setup.lst is one of the files created for your application setup by the Setup Wizard or PDW.
Find $(DLLSelfRegisterEx). You should see $(DLLSelfRegisterEx) highlighted in the entry for MSCal.ocx.
Change $(DLLSelfRegisterEx) to $(DLLSelfRegister).
Save your changes and close Notepad.
Run the application Setup.exe.
i guess that must solve ur problem.
Sameer.
Mr. JPresley,
Till now if u haven't fixed ur problem for application deployment here is the solution, Probably u r using MSCAL.ocx in ur project.that has got an error for self registering. u need to modify ur *.lst file generated by setup.The change u need to make is
Open the Setup.lst file in a text editor, such as Notepad. Setup.lst is one of the files created for your application setup by the Setup Wizard or PDW.
Find $(DLLSelfRegisterEx). You should see $(DLLSelfRegisterEx) highlighted in the entry for MSCal.ocx.
Change $(DLLSelfRegisterEx) to $(DLLSelfRegister).
Save your changes and close Notepad.
Run the application Setup.exe.
i guess that must solve ur problem.
Sameer.
I'm also getting the Application Defined or Object Defined Error 713 as well. To me it seems that some components are not being installed properly yet I get confirmation from the installer that everything has been registered properly. Anyone have any ideas?
Something that may have caused this to happen is when un-installing the new utility (for testing purposes) you may have told the deployment wizard to delete all dependcy files. In other words...if you new application/utility is the only one on your hard-drive using an activeX such as mscal.ocx, then once you uninstall the utilty you'll loose that file, because no other file is currently using it (and I believe it's default to do this).
Search your system folder for the missing files and if they are not there, you'll have to locate the file in the set-up
package directory and copy it to the specific location that it's reference to (i.e. back to the system folder).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.