D
david
Greetings,
I'm doing some modifications of an existing Visual Studio .NET 2003 C#
project that is to be deployed as a windows service. The solution
includes a project that builds an MSI file. Over the month I've been
working on the project, I've built the MSI file many times. Sometimes
it runs fine and I have a service that can be started and stopped.
Other times, the MSI file starts up, goes through several screens and
then reports "The system cannot open the device or file specified".
Additionally, if I run a working file (from an earlier day), it may
succeed or it may fail. So far I've found no pattern to successes or
failures.
I've turned on installer logging (at the 'voicewarmup' level) and see
the following messages from a failure:
DEBUG: Error 2835: The control ErrorIcon was not found on dialog
ErrorDialog
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2835. The arguments are: ErrorIcon, ErrorDialog,
The system cannot open the device or file specified.
MSI (s) () []: MainEngineThread is returning 110
MSI (c) () []: Note: 1: 2755 2: 110 3: C:\80546\My DIM
Service\Release\My DIM Service.msi
MSI (c) () []: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2755: Server returned unexpected error 110 attempting to
install package C:\80546\My DIM Service\Release\My DIM Service.msi.
MSI (c) () []: Note: 1: 2262 2: Error 3: -2147287038
The MSI file name given, i.e. "C:\80546\My DIM Service\Release\My DIM
Service.msi", is truly the name of my MSI file.
As an added complication, the MSI file I built last Monday was fine on
Monday, still fine on Wednesday, and started failing on Thursday.
What the heck is going on here?
Does anybody have information about "Error 2835", "ErrorIcon",
"ErrorDialog", etc?
Does anybody know why some builds succeed and others fail?
How do I make Visual Studio .NET 2003 to produce a good MSI file and do
it every time?
Regards,
David
I'm doing some modifications of an existing Visual Studio .NET 2003 C#
project that is to be deployed as a windows service. The solution
includes a project that builds an MSI file. Over the month I've been
working on the project, I've built the MSI file many times. Sometimes
it runs fine and I have a service that can be started and stopped.
Other times, the MSI file starts up, goes through several screens and
then reports "The system cannot open the device or file specified".
Additionally, if I run a working file (from an earlier day), it may
succeed or it may fail. So far I've found no pattern to successes or
failures.
I've turned on installer logging (at the 'voicewarmup' level) and see
the following messages from a failure:
DEBUG: Error 2835: The control ErrorIcon was not found on dialog
ErrorDialog
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2835. The arguments are: ErrorIcon, ErrorDialog,
The system cannot open the device or file specified.
MSI (s) () []: MainEngineThread is returning 110
MSI (c) () []: Note: 1: 2755 2: 110 3: C:\80546\My DIM
Service\Release\My DIM Service.msi
MSI (c) () []: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2755: Server returned unexpected error 110 attempting to
install package C:\80546\My DIM Service\Release\My DIM Service.msi.
MSI (c) () []: Note: 1: 2262 2: Error 3: -2147287038
The MSI file name given, i.e. "C:\80546\My DIM Service\Release\My DIM
Service.msi", is truly the name of my MSI file.
As an added complication, the MSI file I built last Monday was fine on
Monday, still fine on Wednesday, and started failing on Thursday.
What the heck is going on here?
Does anybody have information about "Error 2835", "ErrorIcon",
"ErrorDialog", etc?
Does anybody know why some builds succeed and others fail?
How do I make Visual Studio .NET 2003 to produce a good MSI file and do
it every time?
Regards,
David