Actually, our problem doesn't have anything to do with an updater scheduled task, but a scheduled task that gets created to do database backups. Either way though, we'll try using [%USERDOMAIN] and see what effect it has.
Thanks for now
Suggested Articles
Search found 71 matches
- Fri Aug 08, 2008 11:58 am
- Forum: Common Problems
- Topic: Updater User Account Default Changed?
- Replies: 4
- Views: 5906
- Jump to post
- Fri Aug 08, 2008 8:50 am
- Forum: Common Problems
- Topic: Updater User Account Default Changed?
- Replies: 4
- Views: 5906
- Jump to post
Re: Updater User Account Default Changed?
Hi Cosmin
Have you heard any more about this? I think I might have the same problem...
Regards,
Have you heard any more about this? I think I might have the same problem...
Regards,
- Wed Jun 25, 2008 8:00 am
- Forum: Common Problems
- Topic: Service Name and event sequence
- Replies: 3
- Views: 4710
- Jump to post
Re: Service Name and event sequence
Hi there
I think your problem is that you're using a private property. Private properties don't get preserved from the UI sequence to the execute sequence. Try using a public property (ie. having a name consisting of capital letters). In your case, ENVIRONMENTNAME or something similar.
I think your problem is that you're using a private property. Private properties don't get preserved from the UI sequence to the execute sequence. Try using a public property (ie. having a name consisting of capital letters). In your case, ENVIRONMENTNAME or something similar.
- Wed Jun 11, 2008 10:48 am
- Forum: Common Problems
- Topic: Hide "sensitive" properties from log
- Replies: 4
- Views: 5862
- Jump to post
Re: Hide "sensitive" properties from log
Hmm. Okay, I suppose I'll have to consider checking the value of that policy during my installation.
Thanks though.
Thanks though.
- Wed Jun 11, 2008 10:30 am
- Forum: Common Problems
- Topic: Hide "sensitive" properties from log
- Replies: 4
- Views: 5862
- Jump to post
Re: Hide "sensitive" properties from log
Bummer.
Trust Microsoft to provide a solution to your problem that doesn't work. The last point in the topic "Preventing Confidential Information from Being Written into the Log File" didn't mention that Debug mode will "ignore" that flag (it only mentions that for "MsiHiddenProperties")...
I ...
Trust Microsoft to provide a solution to your problem that doesn't work. The last point in the topic "Preventing Confidential Information from Being Written into the Log File" didn't mention that Debug mode will "ignore" that flag (it only mentions that for "MsiHiddenProperties")...
I ...
- Tue Jun 10, 2008 4:28 pm
- Forum: Common Problems
- Topic: Hide "sensitive" properties from log
- Replies: 4
- Views: 5862
- Jump to post
Hide "sensitive" properties from log
Hi there guys
I'm using a deferred custom action that I'm passing "sensitive" parameters to. I've read in the MSDN docs that it is possible to set a "flag" called "msidbCustomActionTypeHideTarget" by adding 0x2000 or 8192 to the "Type" column of the custom action. Since you're generating type 51 ...
I'm using a deferred custom action that I'm passing "sensitive" parameters to. I've read in the MSDN docs that it is possible to set a "flag" called "msidbCustomActionTypeHideTarget" by adding 0x2000 or 8192 to the "Type" column of the custom action. Since you're generating type 51 ...
- Tue May 13, 2008 1:25 pm
- Forum: Common Problems
- Topic: Yet another 1627
- Replies: 5
- Views: 7737
- Jump to post
Re: Yet another 1627
I've managed to fix the faulty project file, which seemed to be caused by a custom dialog. Unfortunately I didn't keep a copy of the project file before I deleted the dialog, so I'm not sure why it wasn't working.
Thanks nonetheless.
Thanks nonetheless.
- Tue May 13, 2008 12:22 pm
- Forum: Common Problems
- Topic: Yet another 1627
- Replies: 5
- Views: 7737
- Jump to post
Re: Yet another 1627
Hi guys
Any news on this? It seems we ran into it too:
Creating CAB file(s)... done.
Creating MSI database...
Exception - Error calling Msi API: 1627 Method: MsiViewExecute Table: Control. Extended Error:
1: 2259
Any news on this? It seems we ran into it too:
Creating CAB file(s)... done.
Creating MSI database...
Exception - Error calling Msi API: 1627 Method: MsiViewExecute Table: Control. Extended Error:
1: 2259
- Thu Apr 24, 2008 9:09 am
- Forum: Common Problems
- Topic: User rights and MsiOpenProduct
- Replies: 1
- Views: 3898
- Jump to post
User rights and MsiOpenProduct
Hi there guys (long time!)
Do you have any idea why a call to MsiOpenProduct or MsiEnumRelatedProducts would fail on a limited account? We've got a specific client site where these calls fail, and I can only assume that it is because of some policy setting. Ideas?
Thanks
Do you have any idea why a call to MsiOpenProduct or MsiEnumRelatedProducts would fail on a limited account? We've got a specific client site where these calls fail, and I can only assume that it is because of some policy setting. Ideas?
Thanks
- Mon Mar 03, 2008 2:59 pm
- Forum: Common Problems
- Topic: Error installing to GAC: Error writing to file
- Replies: 2
- Views: 5403
- Jump to post
.- Mon Mar 03, 2008 10:55 am
- Forum: Common Problems
- Topic: Error installing to GAC: Error writing to file
- Replies: 2
- Views: 5403
- Jump to post
Error installing to GAC: Error writing to file
Hi again
We've got one client machine where we've gotten this error:
"Error writing to file: [DllName].dll. Verify that you have access to that directory."
The user account is in the adminitrator group. Gacutil also fails with error: "Unknown Error hr=0X80131107", also with "/f" option. I still ...
We've got one client machine where we've gotten this error:
"Error writing to file: [DllName].dll. Verify that you have access to that directory."
The user account is in the adminitrator group. Gacutil also fails with error: "Unknown Error hr=0X80131107", also with "/f" option. I still ...
- Mon Mar 03, 2008 7:40 am
- Forum: Common Problems
- Topic: VB Script Error.
- Replies: 2
- Views: 4233
- Jump to post
- Wed Feb 27, 2008 2:55 pm
- Forum: Common Problems
- Topic: Patch doesn't apply properly
- Replies: 3
- Views: 5634
- Jump to post
- Wed Feb 27, 2008 2:01 pm
- Forum: Common Problems
- Topic: Patch doesn't apply properly
- Replies: 3
- Views: 5634
- Jump to post
Patch doesn't apply properly
Hi there guys
I've ran into an issue now where a patch we've built applies without fault, but doesn't actually make any changes except to the ARP entries.
I would've abandoned the patch and gone to look at the project file, but I've managed to install the patch correctly if I install it like this ...
I've ran into an issue now where a patch we've built applies without fault, but doesn't actually make any changes except to the ARP entries.
I would've abandoned the patch and gone to look at the project file, but I've managed to install the patch correctly if I install it like this ...
- Wed Feb 06, 2008 7:38 am
- Forum: Common Problems
- Topic: Using /SetVersion from the command line
- Replies: 8
- Views: 10644
- Jump to post
We've developed a workaround for the same problem at our company. It involves having a bootstrap for the MSI which checks what the installed version of the application is, compares it to the version in the new MSI, and if only the build version has been incremented, it uninstalls the old version and ...