This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Error 2835 With Session.Message
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2009
02:24 PM
Error 2835 With Session.Message
Using a VbScript CA I'm trying to post a modal message box using Session.Message BUT trying to use an Error Icon or Critical/Hand Icon. No matter what code I pass into the session message record I can't seem to get anything other then the vbExclamation icon.
I've tried with constants vs. hard code Hex strings (e.g. &H01000010) with no luck.
Here's the VBScript code:
Dim Response
Set hMsgRecord = Session.Installer.CreateRecord(0)
hMsgRecord.StringData(0) = sInvalidInfoError & " must be non-blank in order to proceed."
Response = Session.Message (msiMessageTypeError + vbCritical, hMsgRecord)
Set hMsgRecord = nothing
Here's the error in the MSI log: Line 1 is the function, line 2 is the message I'm displaying.
Action start 14:04:26: ValidateCustomerInfo.
Info 2835.The control ErrorIcon was not found on dialog SetupError.
User name must be non-blank in order to proceed.
MSI (c) (DC!A0) [14:04:27:918]: Product: xxxxxx Database Utility -- User name must be non-blank in order to proceed.
Action ended 14:04:27: ValidateCustomerInfo. Return value 0.
Anyone encounter the same troubles before?
Scott
I've tried with constants vs. hard code Hex strings (e.g. &H01000010) with no luck.
Here's the VBScript code:
Dim Response
Set hMsgRecord = Session.Installer.CreateRecord(0)
hMsgRecord.StringData(0) = sInvalidInfoError & " must be non-blank in order to proceed."
Response = Session.Message (msiMessageTypeError + vbCritical, hMsgRecord)
Set hMsgRecord = nothing
Here's the error in the MSI log: Line 1 is the function, line 2 is the message I'm displaying.
Action start 14:04:26: ValidateCustomerInfo.
Info 2835.The control ErrorIcon was not found on dialog SetupError.
User name must be non-blank in order to proceed.
MSI (c) (DC!A0) [14:04:27:918]: Product: xxxxxx Database Utility -- User name must be non-blank in order to proceed.
Action ended 14:04:27: ValidateCustomerInfo. Return value 0.
Anyone encounter the same troubles before?
Scott
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2009
07:49 PM
Tried &H00002010 ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 24, 2009
10:35 AM
Sorry Cousin Larry, neither &H00001010 nor &H00002010 did anything. It has to be related to that 2835 error.;)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 24, 2009
09:25 PM
I'm not able to reproduce this behavior with the code provided in a sample project. Does the SetupError dialog in your project contain an icon control named ErrorIcon?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 25, 2009
10:08 AM
Nope. just a WarningIcon. I see this in 2 ISMs that have been upgraded through "time" from IS 11-> IS 12-> IS 2008-> 2009-> 2010, etc.
On the newest 2010 ISM I see ErrorIcon and ErrorText so did this change through the years? And what is my course of action at this point? Do I rename WarningIcon to ErrorIcon?:confused:
On the newest 2010 ISM I see ErrorIcon and ErrorText so did this change through the years? And what is my course of action at this point? Do I rename WarningIcon to ErrorIcon?:confused:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 25, 2009
10:29 AM
Renaming that icon to ErrorIcon in the dialog fixed the issue. Is this safe to do?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 25, 2009
10:53 AM
Yes, that should be safe; and yes, it's something that changed around the IS12 era, at least according to KB article Q107830.