Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Sharing violation with MsiShortcutProperty table
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Adrian Accinelli  
View profile  
 More options Oct 15, 2:00 am
Newsgroups: microsoft.public.platformsdk.msi
From: "Adrian Accinelli" <hclnospamali...@newsgroup.nospam>
Date: Wed, 14 Oct 2009 12:00:06 -0400
Local: Thurs, Oct 15 2009 2:00 am
Subject: Sharing violation with MsiShortcutProperty table
With Windows 7 and the introduction of new Taskbar with jumplist etc it is a
good bet that many applications installing using MSI packages will make use
of the MsiShortcutProperty table.  Makes your application shine and all
that...

In some rare circumstances (less than 5% of installs) when using this table
in an MSI I have seen error 1946 come up.  This is a warning really but
typically will stop the install until the user acknowledges it so is an
annoyance.  In each case the associated system error code is 32 which is
ERROR_SHARING_VIOLATION.

It's important to note that this particular problem has nothing to do with
incorrect or badly formatted PropertyKey/PropVariantValue field contents.
The exact same MSI can be installed fine (with correct property values set
in all the LNK files) and then subsequently removed and installed again only
to receive the warning. Similarly after seeing the warning the same install
can succeed twenty more times in succession.

I am interested to know whether or not others have come across this
behaviour.

Sincerely,
Adrian Accinelli


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
dbareis [Windows Installer MVP]  
View profile  
 More options Nov 25, 9:49 am
Newsgroups: microsoft.public.platformsdk.msi
From: "dbareis [Windows Installer MVP]" <dbar...@gmail.com>
Date: Tue, 24 Nov 2009 14:49:30 -0800 (PST)
Local: Wed, Nov 25 2009 9:49 am
Subject: Re: Sharing violation with MsiShortcutProperty table
Hi,

On Oct 15, 3:00 am, "Adrian Accinelli"

<hclnospamali...@newsgroup.nospam> wrote:
> In some rare circumstances (less than 5% of installs) when using this table
> in an MSI I have seen error 1946 come up.  This is a warning really but
> typically will stop the install until the user acknowledges it so is an
> annoyance.  In each case the associated system error code is 32 which is
> ERROR_SHARING_VIOLATION.

My guess is the Windows indexing (or other similar) service and lack
of retries in Windows Installer.

Bye,
Dennis


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google