Error 2356 when adding "Smart Device Programmability" feature

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jim Barry - 29 Aug 2007 14:28 GMT

I originally installed VS2005 without the "Smart Device Programmability" feature. I have since installed SP1. I now need to add the "Smart Device Programmability" feature. I chose "Add or Remove Features" in the installer, added "Smart Device Programmability" under "Visual C++", and hit the Update button. After about 5 minutes of thumb-twiddling, the installer pops up a message saying that it has encountered an unexpected error with code 2356. After another 5 minutes of rolling back (why must everything take so long?), I am invited to view the install log, which looks like this:

[08/29/07,13:52:19] Microsoft Visual Studio 2005 Team Suite - ENU: [2] ERROR:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2356.
[08/29/07,13:52:19] Microsoft Visual Studio 2005 Team Suite - ENU: [2] ACTION FAILURE:Action ended 13:52:19: InstallFinalize. Return value 3.See MSI log for details.
[08/29/07,13:52:20] Microsoft Visual Studio 2005 Team Suite - ENU: [2] ACTION FAILURE:Action ended 13:52:20: INSTALL. Return value 3.See MSI log for details.
[08/29/07,13:56:42] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[08/29/07,13:56:42] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[08/29/07,13:56:43] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite - ENU is not installed.
[08/29/07,13:56:43] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0

I have tried it by mounting the ISO as a drive, and by extracting the ISO contents onto my hard drive. The error is the same either way. I have verified that the SHA-1 hash of the ISO is correct.

Is it not possible to add features after having applied SP1? I really don't want to have to uninstall/reinstall and go through the SP1 nightmare again. It would take a whole day.

Signature

Jim Barry, MVP (Windows SDK)

Reply to this Message

Steven Cheng[MSFT] - 30 Aug 2007 05:49 GMT

Hi Jim,

From your description, you're encoutering some problem when try add the
"Smart Device programmability" to the VS 2005 suites (after applied SP1),
correct?

According to the error log you provided, I've performed some research in
some former cased, it seems haven't found any records exactly match this.
In addition to launch the setup wizard through "add/remove programs" panel,
have you also tried directly launch the VS 2005 setup (msi or exe) to add
the smart device dev feature to see whether it works? Of course, add new
features after applied SP1 is supported cases.

Also, for the setup error, I suggest you locate the verbose log file. By
default, verbose logging is turned on for the Visual Studio 2005
installation. The log file is named VSMsiLog*.txt. The asterisk (*)
represents the four alphanumeric characters in the file name. For example,
the file name may be similar to VSMSILogA1d1.txt. The file is approximately
40 megabytes (MB).

It may be in %TEMP% or C:\Program Files (x86)\Microsoft Visual Studio
8\Common7\LogFiles

you can also find more information about troubleshooting VS 2005 setup
issues in the following kb article:

http://support.microsoft.com/?id=904732

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>From: "Jim Barry" <jbarry@newsgroup.nospam>
>Subject: Error 2356 when adding "Smart Device Programmability" feature

>I originally installed VS2005 without the "Smart Device Programmability" feature. I have since installed SP1. I now need to add the "Smart Device

Programmability" feature. I chose "Add or Remove Features" in the
installer, added "Smart Device Programmability" under "Visual C++", and hit
the Update button. After about 5 minutes of thumb-twiddling, the installer
pops up a message saying that it has encountered an unexpected error with
code 2356. After another 5 minutes of rolling back (why must everything
take so long?), I am invited to view the install log, which looks like this:

>[08/29/07,13:52:19] Microsoft Visual Studio 2005 Team Suite - ENU: [2] ERROR:The installer has encountered an unexpected error installing this

package. This may indicate a problem with this package. The error code is
2356.

>[08/29/07,13:52:19] Microsoft Visual Studio 2005 Team Suite - ENU: [2]

ACTION FAILURE:Action ended 13:52:19: InstallFinalize. Return value 3.See
MSI log for details.

>[08/29/07,13:52:20] Microsoft Visual Studio 2005 Team Suite - ENU: [2] ACTION FAILURE:Action ended 13:52:20: INSTALL. Return value 3.See MSI log

for details.

>[08/29/07,13:56:42] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
>[08/29/07,13:56:42] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
>[08/29/07,13:56:43] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite - ENU is not installed.
>[08/29/07,13:56:43] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0
>I have tried it by mounting the ISO as a drive, and by extracting the ISO contents onto my hard drive. The error is the same either way. I have

verified that the SHA-1 hash of the ISO is correct.

>Is it not possible to add features after having applied SP1? I really don't want to have to uninstall/reinstall and go through the SP1 nightmare

again. It would take a whole day.

Reply to this Message

Jim Barry - 30 Aug 2007 11:25 GMT

> From your description, you're encoutering some problem when try add
> the "Smart Device programmability" to the VS 2005 suites (after
> applied SP1), correct?

Yes, exactly right.

> According to the error log you provided, I've performed some research
> in some former cased, it seems haven't found any records exactly
> match this. In addition to launch the setup wizard through
> "add/remove programs" panel, have you also tried directly launch the
> VS 2005 setup (msi or exe) to add the smart device dev feature to see
> whether it works?

I tried it both ways but the same thing happens in each case.

> Of course, add new features after applied SP1 is
> supported cases.

So how does that work? After adding new features, am I supposed to apply SP1 again?

> Also, for the setup error, I suggest you locate the verbose log file.
> By default, verbose logging is turned on for the Visual Studio 2005
> installation. The log file is named VSMsiLog*.txt. The asterisk (*)
> represents the four alphanumeric characters in the file name.

OK, I found the log in the temp directory. The problem seems to be something to do with installing fonts. Here is the relevant section of the log. If you want the whole log, I can email it to you but it is nearly 17 MB.

MSI (s) (D0:6C) [13:51:06:109]: File: C:\WINDOWS\Fonts\nina.ttf; To be installed; Won't patch; No existing file
MSI (s) (D0:6C) [13:51:06:109]: Source for file '_1D770F0F19D347F899735ECCFB70654B.C323BADC26484E2BBBB9655802778362' is compressed
MSI (s) (D0:6C) [13:51:06:109]: SOFTWARE RESTRICTION POLICY: Verifying object --> 'C:\WINDOWS\Installer\438a747.msi' against software restriction policy
MSI (s) (D0:6C) [13:51:06:109]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\438a747.msi has a digital signature
MSI (s) (D0:6C) [13:51:06:265]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\438a747.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (D0:C4) [13:51:06:265]: Note: 1: 2262 2: _13273_VSDFonts.msm 3: -2147287038
MSI (s) (D0:6C) [13:51:06:265]: Note: 1: 2356 2: _13273_VSDFonts.msm
MSI (s) (D0:6C) [13:51:06:312]: Transforming table Error.
MSI (s) (D0:6C) [13:51:06:328]: Transforming table Error.
MSI (s) (D0:6C) [13:51:06:328]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2356: Couldn't locate cabinet in stream: _13273_VSDFonts.msm.
MSI (s) (D0:6C) [13:52:19:578]: Transforming table Error.
MSI (s) (D0:6C) [13:52:19:593]: Transforming table Error.
MSI (s) (D0:6C) [13:52:19:593]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (D0:6C) [13:52:19:609]: Product: Microsoft Visual Studio 2005 Team Suite - ENU -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2356. The arguments are: _13273_VSDFonts.msm, ,

Signature

Jim Barry, MVP (Windows SDK)

Reply to this Message

Steven Cheng[MSFT] - 03 Sep 2007 05:27 GMT

Thanks for your reply Jim,

So the further log indicate that ""Couldn't locate cabinet in stream:", it
seems the setup package could be corrupted. Have you tried install through
the original CDROM media?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>From: "Jim Barry" <jbarry@newsgroup.nospam>
>References: <OjcCvBk6HHA.2312@TK2MSFTNGP06.phx.gbl>

<KqBBBFs6HHA.6140@TK2MSFTNGHUB02.phx.gbl>

>Subject: Re: Error 2356 when adding "Smart Device Programmability" feature

>> From your description, you're encoutering some problem when try add
>> the "Smart Device programmability" to the VS 2005 suites (after
[quoted text clipped - 15 lines]
>> represents the four alphanumeric characters in the file name.
>OK, I found the log in the temp directory. The problem seems to be something to do with installing fonts. Here is the relevant section of the

log. If you want the whole log, I can email it to you but it is nearly 17
MB.

>MSI (s) (D0:6C) [13:51:06:109]: File: C:\WINDOWS\Fonts\nina.ttf; To be installed; Won't patch; No existing file
>MSI (s) (D0:6C) [13:51:06:109]: Source for file '_1D770F0F19D347F899735ECCFB70654B.C323BADC26484E2BBBB9655802778362' is

compressed

>MSI (s) (D0:6C) [13:51:06:109]: SOFTWARE RESTRICTION POLICY: Verifying object --> 'C:\WINDOWS\Installer\438a747.msi' against software restriction

policy

>MSI (s) (D0:6C) [13:51:06:109]: SOFTWARE RESTRICTION POLICY:

C:\WINDOWS\Installer\438a747.msi has a digital signature

>MSI (s) (D0:6C) [13:51:06:265]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\438a747.msi is permitted to run at the 'unrestricted'

authorization level.

>MSI (s) (D0:C4) [13:51:06:265]: Note: 1: 2262 2: _13273_VSDFonts.msm 3: -2147287038
>MSI (s) (D0:6C) [13:51:06:265]: Note: 1: 2356 2: _13273_VSDFonts.msm
[quoted text clipped - 6 lines]
>MSI (s) (D0:6C) [13:52:19:593]: Note: 1: 2262 2: Error 3: -2147287038
>MSI (s) (D0:6C) [13:52:19:609]: Product: Microsoft Visual Studio 2005 Team Suite - ENU -- The installer has encountered an unexpected error installing

this package. This may indicate a problem with this package. The error code
is 2356. The arguments are: _13273_VSDFonts.msm, ,

Reply to this Message

Jim Barry - 03 Sep 2007 11:53 GMT

> So the further log indicate that ""Couldn't locate cabinet in
> stream:", it seems the setup package could be corrupted. Have you
> tried install through the original CDROM media?

Yes, I have tried it with the original MSDN disc and it fails in exactly the same way. As I mentioned, I also downloaded the ISO image and verified the SHA-1 hash, so we can be 100% certain that the problem is definitely not caused by corrupted media.

Signature

Jim Barry, MVP (Windows SDK)

Reply to this Message

Jim Barry - 04 Sep 2007 13:18 GMT

Hi Steven,

Any ideas, or is it time to embark on a full reinstall?

Thanks

Steven Cheng[MSFT] wrote:

> So the further log indicate that ""Couldn't locate cabinet in
> stream:", it seems the setup package could be corrupted. Have you
> tried install through the original CDROM media?

Signature

Jim Barry, MVP (Windows SDK)

Reply to this Message

Steven Cheng[MSFT] - 05 Sep 2007 04:50 GMT

Hi Jim,

I'll try lookup the error message in our internal cases db to see whether
there is any similar issue first. I'll let you know soon.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>From: "Jim Barry" <jbarry@newsgroup.nospam>
>
[quoted text clipped - 6 lines]
>> tried install through the original CDROM media?
>Yes, I have tried it with the original MSDN disc and it fails in exactly the same way. As I mentioned, I also downloaded the ISO image and verified

the SHA-1 hash, so we can be 100% certain that the problem is definitely
not caused by corrupted media.

Reply to this Message

Steven Cheng[MSFT] - 11 Sep 2007 09:14 GMT

Hi Jim,

Sorry for the late reponse as I was on sick previous days. Just inform you
that I'm still contacting some other VS 2005 SP1 setup related engineers on
this issue, and will update you if I get any new information from them.

Also, if you feel it maybe too long and you'll go through the issue soon, I
agree that you can consider perform a thorough reinstallation.

Thanks for your understanding.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>From: stcheng@online.microsoft.com (Steven Cheng[MSFT])
>Organization: Microsoft
>Date: Wed, 05 Sep 2007 03:50:52 GMT
>Subject: Re: Error 2356 when adding "Smart Device Programmability" feature

>Hi Jim,
>
[quoted text clipped - 25 lines]
>the SHA-1 hash, so we can be 100% certain that the problem is definitely
>not caused by corrupted media.

Reply to this Message

Steven Cheng[MSFT] - 13 Sep 2007 03:53 GMT

Hi Jim,

How are you doing? Have you taken further actions on this. After discussing
with some VS 2005 and SP1 related engineers, they also haven't any definite
idea and agree that it's necessary to view the detailed log so as to get
more values. Anyway, due to the newsgroup communication restriction, it
would be quite inefficent for such issue. Maybe perform a thorough
reinstall would be a quick solution. How do you think?

Please feel free to let me know if there is anything else we can help.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>Date: Tue, 11 Sep 2007 08:14:06 GMT
>Subject: Re: Error 2356 when adding "Smart Device Programmability" feature

>Hi Jim,
>
[quoted text clipped - 52 lines]
>>the SHA-1 hash, so we can be 100% certain that the problem is definitely
>>not caused by corrupted media.

Reply to this Message

Jim Barry - 17 Sep 2007 11:13 GMT

> How are you doing? Have you taken further actions on this. After
> discussing with some VS 2005 and SP1 related engineers, they also
[quoted text clipped - 3 lines]
> issue. Maybe perform a thorough reinstall would be a quick solution.
> How do you think?

Hi Steven,

I just got back from a week's holiday. I really do need to start work on some CE development so unless you can come up with anything I guess I'll have to get on with the uninstall/reinstall (though I wouldn't call it a quick solution). I'm still interested to know what the reason is for the installer error. Can I send you the full log by email?

Signature

Jim Barry, MVP (Windows SDK)

Reply to this Message

Jim Barry - 18 Sep 2007 18:14 GMT

First I tried a repair install, which failed with error 2356 (though for a different package than before). Next I completely uninstalled VS 2005, which completed with unspecified errors. I then reinstalled VS 2005 and it completed, but said that installation had failed for "Microsoft Device Emulator version 1.0". Oddly, the device emulator is actually present and appears to be working. Not being quite sure what to do next, I decided to press on and install SP1, which is chugging away now and taking so long that it will have to be left to complete overnight.

Signature

Jim Barry, MVP (Windows SDK)

Reply to this Message

Error 2356 when adding "Smart Device Programmability" feature

Free Magazines