Weird error - does not appear in log
I'm looking for some help. I have a package with a transform that I created. Everything seems to work just fine, but at the end of the installation, even though a dialog pops up stating that the installation has completed successfully, I get a seperate dialog (that isn't in the package) that pops up with a heading of:
Error in _WriteStrToLog: MsiCreateRecord failed to create a record.
The dialog in the error message simply states:
MsiCreateRecord
And there is only an OK button in the dialog. There is another message that appears after I click "OK" and it shows with the following header:
MsiProcessMessage
Dialog:
Error in _WriteStrToLog: MsiProcessMessage failed. An invalid parameter or handle was supplied. Return Code=-1
Now, here's the thing. I've logged verbose (/l*v) and don't see anything related to this message. I don't see anything in the Event Viewer relating to this message. I've even gone to the point of starting a new MST, changing only two, what should be insignificant items (in Wise Installation Expert I changed it to "Never Reboot" and I changed the Comment under General Information) ran the install and got the same error messages. Conversly, after this, I created another new MST, changed the same two items, ran the installation and DIDN'T get the error messages (same command-line for all installs)
Anyone have any idea? Everything else in the package works fine and this will be deployed via SCCM and silent install, but you can still see flashes on a /qn install when those errors pop up, even when running from a command line as the SYSTEM account. Functionally, it's fine, but I tend to be very particular with my packaging and I don't want to push out a pilot until this is fixed. Thanks in advance for the help.
Error in _WriteStrToLog: MsiCreateRecord failed to create a record.
The dialog in the error message simply states:
MsiCreateRecord
And there is only an OK button in the dialog. There is another message that appears after I click "OK" and it shows with the following header:
MsiProcessMessage
Dialog:
Error in _WriteStrToLog: MsiProcessMessage failed. An invalid parameter or handle was supplied. Return Code=-1
Now, here's the thing. I've logged verbose (/l*v) and don't see anything related to this message. I don't see anything in the Event Viewer relating to this message. I've even gone to the point of starting a new MST, changing only two, what should be insignificant items (in Wise Installation Expert I changed it to "Never Reboot" and I changed the Comment under General Information) ran the install and got the same error messages. Conversly, after this, I created another new MST, changed the same two items, ran the installation and DIDN'T get the error messages (same command-line for all installs)
Anyone have any idea? Everything else in the package works fine and this will be deployed via SCCM and silent install, but you can still see flashes on a /qn install when those errors pop up, even when running from a command line as the SYSTEM account. Functionally, it's fine, but I tend to be very particular with my packaging and I don't want to push out a pilot until this is fixed. Thanks in advance for the help.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
andys0123
12 years ago
Does the log show the installation was successful?
As you managed to create an MST that didn't give the error, it sounds like your original MSTs were corrupt. Were they all created on the same machine? Did you restart Wise before the successful MST was created? I have had the odd MSI/MSt that failed for unknown reasons, even after trimming back to basics and after starting afresh, all has worked fine.
If need be, you could set your SCCM Program to run 'Hidden' so that the user doesn't see anything.
As you managed to create an MST that didn't give the error, it sounds like your original MSTs were corrupt. Were they all created on the same machine? Did you restart Wise before the successful MST was created? I have had the odd MSI/MSt that failed for unknown reasons, even after trimming back to basics and after starting afresh, all has worked fine.
If need be, you could set your SCCM Program to run 'Hidden' so that the user doesn't see anything.
Posted by:
anonymous_9363
12 years ago
I have had the odd MSI/MSt that failed for unknown reasons, even after trimming back to basics and after starting afresh, all has worked fine.Ditto. Many times.
Posted by:
WBrady
12 years ago
Log shows successful installation.
I created NEW MST files from the base MSI on a clean Virtual Machine (i.e, reverted to original clean state before copying over MSI and creating new transform) so while they were created on the same machine, each one was created in an independent environment.
What's confusing to me is that creating a new transform seems to work, provided I don't change anything at all, but at some random point, it gets corrupted. So my situation pretty much looks like this (all 4 transforms were created on fresh VMs and completely seperately from one another:)
MST #1.) Corrupted after 4 hours of work, almost complete repackaging including splitting DLLs to their own components. Fine until this point
MST #2.) Corrupted after 2 edits.
MST #3.) Corrupted after 1 hour of work, basic changes (adding missing keys to components, beginning to split DLLs out...)
MST #4.) Corrupted after creation and save.
This is why it's so confusing to me. There isn't a single edit I can tie the corruption to. It's not as if I edit a table or a value and Boom, it goes bezerk. It's also on a VM that I've been using without fail for quite some time (though I do patch it) and the installation seems completely successful outside of this stupid error message. Yes, I know I can run it as "Hidden" in SCCM, but it bugs me. I like to have things clean and perfect. The problem is that with the number of major infrastructure projects I'm working on, I'm running out of time that I can justify, and no offense to my co-workers as I like them very much, but if I can't figure this out, it's highly unlikely that one of them will be able to.
I created NEW MST files from the base MSI on a clean Virtual Machine (i.e, reverted to original clean state before copying over MSI and creating new transform) so while they were created on the same machine, each one was created in an independent environment.
What's confusing to me is that creating a new transform seems to work, provided I don't change anything at all, but at some random point, it gets corrupted. So my situation pretty much looks like this (all 4 transforms were created on fresh VMs and completely seperately from one another:)
MST #1.) Corrupted after 4 hours of work, almost complete repackaging including splitting DLLs to their own components. Fine until this point
MST #2.) Corrupted after 2 edits.
MST #3.) Corrupted after 1 hour of work, basic changes (adding missing keys to components, beginning to split DLLs out...)
MST #4.) Corrupted after creation and save.
This is why it's so confusing to me. There isn't a single edit I can tie the corruption to. It's not as if I edit a table or a value and Boom, it goes bezerk. It's also on a VM that I've been using without fail for quite some time (though I do patch it) and the installation seems completely successful outside of this stupid error message. Yes, I know I can run it as "Hidden" in SCCM, but it bugs me. I like to have things clean and perfect. The problem is that with the number of major infrastructure projects I'm working on, I'm running out of time that I can justify, and no offense to my co-workers as I like them very much, but if I can't figure this out, it's highly unlikely that one of them will be able to.
Posted by:
andys0123
12 years ago
Try creating a simple Transform using Orca. This should show whether it's a Wise thing or something strange with the MSI.
Posted by:
WBrady
12 years ago
Sigh.
Okay. So, and I apologize for not getting back to you sooner, but some scheduled tasks were failing and well, duty calls. Anyway...
I created a simple transform in Orca and changed only 2 things. Saved, tested, worked great. Then, though I was skeptical, I went through the painstaking work of assigning some of the components that were missing keypaths, correct keypaths. Saved, tested and...
No dice. Same errors. I maybe added 10 or so keypaths - I ran ICE validation to check my work, and it was clean (at least my work was, not the rest of the package [:D] )
So... I'm back to where I was before. The way I see it right now, I have two options. 1.) Continue with my current package and test the deployment via SCCM and deal with seemingly minor issue of the error messages flashing on the screen and the msiexec process being held hostage for a bit longer than it takes the actual install to occur or 2.) Contact the vendor and report this as a bug, as something corrupt in their original installation package (which doesn't tend to bode well as they'll want everyone in the enterprise to just download it themselves from our VOIP server as a solution... yuck)
Any thoughts, opinions, anything else that I might be missing?
Thanks in advance!
Okay. So, and I apologize for not getting back to you sooner, but some scheduled tasks were failing and well, duty calls. Anyway...
I created a simple transform in Orca and changed only 2 things. Saved, tested, worked great. Then, though I was skeptical, I went through the painstaking work of assigning some of the components that were missing keypaths, correct keypaths. Saved, tested and...
No dice. Same errors. I maybe added 10 or so keypaths - I ran ICE validation to check my work, and it was clean (at least my work was, not the rest of the package [:D] )
So... I'm back to where I was before. The way I see it right now, I have two options. 1.) Continue with my current package and test the deployment via SCCM and deal with seemingly minor issue of the error messages flashing on the screen and the msiexec process being held hostage for a bit longer than it takes the actual install to occur or 2.) Contact the vendor and report this as a bug, as something corrupt in their original installation package (which doesn't tend to bode well as they'll want everyone in the enterprise to just download it themselves from our VOIP server as a solution... yuck)
Any thoughts, opinions, anything else that I might be missing?
Thanks in advance!
Posted by:
anonymous_9363
12 years ago
I'm willing to bet you have a) quite an old version of Wise (pre v7, perhaps?) and b) Quick Compile switched on. Neither of things is good!
Posted by:
WBrady
12 years ago
Okay, I didn't do a very good job of explaining in my last post. The last transform that I made, I edited completely in Orca, so I didn't touch it with WPS at all, and I still received the error. In other words, Orca/WPS have same result (though for the record, we're on WPS 8 and Quick Compile doesn't appear to be a function of an .MST unless you're talking about the "Don't update or recompress files when saving" checkbox, in which case I always leave that unchecked).
As it is, I'm going to see if the vendor has a different package or else just try rolling what I have out since there doesn't appear to be anything that I can do to eliminate this issue from occuring.
As it is, I'm going to see if the vendor has a different package or else just try rolling what I have out since there doesn't appear to be anything that I can do to eliminate this issue from occuring.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.