Groups | Blog | Home
all groups > visual studio .net setup > august 2007 >

visual studio .net setup : Install VS2005 professional fail



Andreas
8/8/2007 2:04:49 AM
During the installation of vs2005 I got the error messsage which is in
following.
Searching in newsgroups for "CA_SetPidProps" show that this error happens
also some other users, but there was no suggestion to solve the problem.

The installation on the PC of colleague with a simalar PC and software
configuration worke without a problem.

What is wrong with my system ?
Could there be a problem with the crypto service ?


Best regards,
Andreas


OS: Windows XP SP2 German
Other installed Versions: VS6.0, VS2003
To install Version: VS2005 prof German


Error text from VSSWMSISummary.txt:
Aktion beendet um 13:28:49: CA_SetEditionType. Rückgabewert 1.
MSI (s) (F0:08) {13:28:49:640}: Machine policy value 'MaxPatchCacheSize' is 10
Aktion gestartet um 13:28:49: CostInitialize.
MSI (s) (F0:08) {13:28:49:640}: PROPERTY CHANGE: Adding ROOTDRIVE property.
Its value is 'T:\'.
MSI (s) (F0:08) {13:28:49:781}: PROPERTY CHANGE: Adding CostingComplete
property. Its value is '0'.
MSI (s) (F0:08) {13:28:49:796}: Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (F0:08) {13:28:49:796}: Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI (s) (F0:08) {13:28:49:796}: Note: 1: 2205 2: 3: MsiPatchHeaders
MSI (s) (F0:08) {13:28:49:796}: Note: 1: 2205 2: 3: __MsiPatchFileList
MSI (s) (F0:08) {13:28:49:796}: Skipping action:
DDSE_CA_Uninstall_CostInitializePost (condition is false)
MSI (s) (F0:08) {13:28:49:796}: Doing action: CA_SetPidProps
Aktion beendet um 13:28:49: CostInitialize. Rückgabewert 1.
MSI (s) (F0:7C) {13:28:49:812}: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI11A.tmp, Entrypoint: SetPidProps
Aktion gestartet um 13:28:49: CA_SetPidProps.
08/01/07 13:28:49 DDSet_Status: LANGID: 1031
08/01/07 13:28:49 DDSet_Entry: SetPidProps started
08/01/07 13:28:49 DDSet_Status: PIDSEQ: 9000000
08/01/07 13:28:49 DDSet_Status: PIDRET: 0
MSI (s) (F0:7C) {13:28:49:843}: Leaked MSIHANDLE (7) of type 790531 for
thread 1300
MSI (s) (F0:7C) {13:28:49:843}: Note: 1: 2769 2: CA_SetPidProps 3: 1
08/01/07 13:28:49 DDSet_Status: EDITIONTYPE: pro
DEBUG: Error 2769: Custom Action CA_SetPidProps did not close 1 MSIHANDLEs.
Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten.
Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist
2769. Argumente: CA_SetPidProps, 1,
Aktion beendet um 13:28:49: CA_SetPidProps. Rückgabewert 3.
Aktion beendet um 13:28:49: INSTALL. Rückgabewert 3.
Property(S): REDISTFOUNDVER = #1
Property(S): DiskPrompt = [1]
Property(S): FeatureID = 1
stcheng NO[at]SPAM online.microsoft.com
8/9/2007 2:45:48 AM
Hi Andreas,

From your description, you're encountering some error when try installing
the Visual Studio 2005 professional on your dev box,correct?

Accordin to the setup log and error info you provided, it seems the log
text are in German. I've picked the core error message (about the
"CA_SetPidProps" custom action) and performed some research in our internal
database and found some record on the similar issue. One of the record has
the following symptom:

[quoted text, click to view]
*** Problem Description ***
When installing Visual Studio 2005 Standard Edition and getting the error
¡°Setup Failed¡±.
Customer had earlier visual Studio 2005 beta on the computer which has now
been
uninstalled.
From MSI log
===============
MSI (s) (40:18) [18:47:21:346]: Leaked MSIHANDLE (3) of type 790531 for
thread
4108
MSI (s) (40:18) [18:47:21:346]: Note: 1: 2769 2: CA_SetPidProps 3: 1
06/07/06 18:47:21 DDSet_Status: EDITIONTYPE: std
DEBUG: Error 2769: Custom Action CA_SetPidProps did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package.
This may
indicate a problem with this package. The error code is 2769. The arguments
are:
CA_SetPidProps, 1,
Action ended 18:47:21: CA_SetPidProps. Return value 3.
[quoted text, click to view]

So do you also have ever installed a beta version of the VS 2005 on that
box? The record indicate that there're some certain services in the
operating system get messed and it will require us to repair the operating
system and service pack to resolve the issue.

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.






Andreas
8/14/2007 2:18:01 AM
Hi Steven,

I haven't installed beta of VS2005.
So I tried to repair the operating system.
The result is the same with the difference that now all updates of Windows
XP SP2 have to be reinstalled.

Is there a dependency to other application ?
I compared the installed software to that of my colleagues and deinstall all
software which was different, but the error occured also.

What could I do to solve problem ?

Best regards,
Andreas


stcheng NO[at]SPAM online.microsoft.com
8/16/2007 4:35:43 AM
Hi Andreas,

Thanks for your reply.

I'm sorry to hear that the problem still remains. Normally Visual Studio
2005 should be a standalone program which won't rely on other program's
installation, however, there did have some issues that some 3rd party
software may incorrrectly modify the environment variables(such as registry
or file ) of the Visual Studio program. If this is the cause, that won't be
quite hard to locate the root cause as we can no longer get it through an
expected approach routine.

Also, you mentioned that the same error remain even after you've performed
the operating system repair, that does make the problem quite tough.
Anyway, I'll ask some other setup engineers to see whether they still have
any idear or comments on such scenario. However, it is probably that you
may need to perform a thorough install since the operating system
enviornment may somewhat get corrupted. I'll let you know as soon as I get
any new information.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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


stcheng NO[at]SPAM online.microsoft.com
8/17/2007 12:00:00 AM
Hi Andreas,

Sorry for keep you waiting.

I've just got some further information on this. Another possible cause of
the issue is that a certain folder of Microsoft software under system
directory is missing. Here is the detailed info:

[quoted text, click to view]

This problem can happen if you are missing the following folder:

C:\Windows\System32\Microsoft

or

C:\WINNT\System32\Microsoft

To resolve the issue, check the System32 folder. You will most likely find
a file
with the name Microsoft and no extension. Delete this file, then restart
Windows.
Windows should re-write the file on its own. After restarting Windows, try
the
VS.NET 2005 installation again.
<<<<<<<<<<<<<<<<<<<<

Here is a kb article about manually remove VS 2005:

How to remove Visual Studio 2005
http://support.microsoft.com/kb/907965

Hope this also helps some.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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


Andreas
8/17/2007 3:32:04 AM
Hi Steven,

thank you very much for the reponse.

On my system the directoty \system32\microsoft exist.
But with regard to your idea to delete the microsoft file,
I am delete the directory microsoft. But the error still occure.

With regard to kb article 907965 "Manually remove VS 2005",
I am checked my PC. The only application which was installed,
was the document explorer. After manually removing this the
error still occure.

I am also removed VS2003 and VC++ 6.0 from my PC, but
the result was also the same.


Best regards,
Andreas


Andreas
8/20/2007 1:34:03 AM
Hello Steven,

thank you for the response.

I am create a new user as administrator and start VS2005 install.
The error is the same.

The machine is also not very ristricted. During the installation process
was all security software (firewall, virus scanner,..) deactivated.

I will now do a clean new installation of OS and will post the result here.


Best regards,
Andreas



stcheng NO[at]SPAM online.microsoft.com
8/20/2007 7:12:42 AM
Thanks for the followup Andreas,

It's a pity that the problem still not resolved. For the status now, I've
discussed with some other engineers, I'm afraid we haven't any definite
clues on this. One thing you can still have a try is logon via a different
account (with different user profile) and perform the same test).

Anyway, I think the problem has become quite tough and hard to
troubleshoot. Not sure whether the problem machine is a very restricted
one. If possible, I think peforming a cleanup and reinstall over the entire
OS will be a more straightforward solution currently. How do you think?

If there is anything else we can help, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



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

stcheng NO[at]SPAM online.microsoft.com
8/21/2007 2:32:36 AM
Thanks for your reply Andreas,

Sure. Please feel free to let me know if you have got any new results.
It is a pity that we haven't been able to get it work without performing
the complete OS recast.

Thanks for your understanding and patience!

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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

AddThis Social Bookmark Button