XNA Game studio 3.0 install issue

---

I've split this post into a new thread because it is a completely different installation issue than the thread it was originally posted on, and I want to try to avoid confusion.  This crash information indicates that there is something wrong in the System.Drawing namespace when XNA Game Studio attempts to display its first UI page (XNA Game Studio setup uses WinForms UI).

The first thing I'd suggest is to try to run XNA Game Studio setup in silent mode to see if that will let you work around this issue.  To do that, you can run the following:

xnags30_setup.exe /quiet

If that doesn't help, then can you try to open Visual C# 208 Express Edition, create a simple Windows Forms application and see if you can run it.  If that crashes too, please let us know what the full call stack says.  It is possible that you're running into an issue similar to the one in this forum post (which links to this Visual Studio forum post).  Those forum posts describe a crash in WinForms that can be caused by having certain applications or devices installed on your system (for example, some older versions of the Logitech QuickCam software caused the issue for a few customers in those posts).  Without a call stack, we can't tell for sure whether you're hitting a similar issue or not.

Thanks!

I have the same issue. I tried the /quite thing but it doesn't help. I also tried creating simple WinForms app. It works so I don't think it is WinForms bug.

Could you please use Visual Studio to gather a full callstack for this crash and post it here so we can take a look?

Also, I've posted a set of steps in the forum post at http://forums.xna.com/forums/p/23626/130166.aspx#130166 that can be used to bypass bootstrapper.exe and get XNA Game Studio 3.0 installed in order to work around this issue.

Thanks!

Here is what I get in a callstack:

Bootstrapper.exe!Microsoft.Xna.TaskManagement.TaskScheduler.RunTasks(string taskListId = "Install", string stateFileName = "state.xml") + 0x408 bytes    
Bootstrapper.exe!Bootstrapper.InstallModeTMEThread.CallTME(object formData) + 0x9a bytes    
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x83 bytes    
mscorlib.dll!System.Threading.ExecutionContext.runTryCode(object userData) + 0x51 bytes    
[Native to Managed Transition]    
[Managed to Native Transition]    
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x67 bytes    
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x45 bytes    
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart(object obj) + 0x4a bytes   

I tried these steps you have mentioned. It works. Thanks.

Thanks for posting the call stack.  A couple other questions:

• Do you get the same ArgumentException as the person who posted the first item in this thread?
• Do you get any log files created in the folder %temp%\XNA Game Studio 3.0 Setup on your system?

Thanks!

Here is what I get:

An unhandled exception of type 'Microsoft.WindowsInstaller.InstallerException' occurred in Bootstrapper.exe
Additional information: The configuration data for this product is corrupt. Contact your support personnel.

No log in %temp%\XNA Game Studio 3.0.

I suppose it is the same problem with the installer discussed before.

Thank you, this helps narrow it down further.  What OS is this happening on?  Also, do you see any information in your application event log for this error (hopefully to help narrow down which Windows Installer product the configuration data is corrupt for)?

Thanks!

Vista Business.

The following information is available in the event log:

Fault bucket 370253939, type 5
Event Name: CLR20r3
Response: None
Cab Id: 0

Problem signature:
P1: bootstrapper.exe
P2: 3.0.0.0
P3: 48f00509
P4: Bootstrapper
P5: 3.0.0.0
P6: 48f00509
P7: 2f6
P8: 23
P9: T0EN5SRQCCK32F2BZAUL3SCJ3WGV0G42
P10:

Here is the error report:

Version=1
EventType=CLR20r3
EventTime=128774743402217559
ReportType=2
Consent=1
UploadTime=128774743432637559
Response.BucketId=370253939
Response.BucketTable=5
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=bootstrapper.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=3.0.0.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=48f00509
Sig[3].Name=Problem Signature 04
Sig[3].Value=Bootstrapper
Sig[4].Name=Problem Signature 05
Sig[4].Value=3.0.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=48f00509
Sig[6].Name=Problem Signature 07
Sig[6].Value=2f6
Sig[7].Name=Problem Signature 08
Sig[7].Value=23
Sig[8].Name=Problem Signature 09
Sig[8].Value=T0EN5SRQCCK32F2BZAUL3SCJ3WGV0G42
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6001.2.1.0.256.6
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1044
UI[2]=c:\935ee03c96bff3a2bb9c8ae9\Bootstrapper.exe
UI[3]=Bootstrapper has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Bootstrapper
AppPath=c:\935ee03c96bff3a2bb9c8ae9\Bootstrapper.exe
ReportDescription=Stopped working

Just to confirm, do you see any entries in your Application event log from the MsiInstaller source around the time of this crash?

Thanks!

There are two entries from the MsiInstaller before the crash entry.

1) Product: Microsoft XNA Game Studio 3.0 (Redists) -- Configuration completed successfully.

2) Windows Installer reconfigured the product. Product Name: Microsoft XNA Game Studio 3.0 (Redists). Product Version: 3.0.11010.0. Product Language: 1033. Reconfiguration success or error status: 0.

Thanks!  One other question - I noticed in your previous reply about log files that you mentioned a folder named "%temp%\XNA Game Studio 3.0"  The logs for XNA Game Studio 3.0 are actually in a folder named "%temp%\XNA Game Studio 3.0 Setup" and the interesting ones appear in a sub-folder named "%temp%\XNA Game Studio 3.0 Setup\Logs"  Do you see any logs in either of those folders?

Also, would it be possible for you to run the steps listed in this blog post to gather a list of installed MSIs on your system and post that to a file server so I could take a quick look and see if I can spot anything problematic in there?

Thanks!

hello, any solution to this problem?? I have windows XP and have tried installing with service pack 1 and 2, but i get the bootstrapper error...

There are several possible causes of bootstrapper.exe crashing.  Can you please gather and post your call stack so we can try to narrow it down further?

One note - XNA Game Studio setup requires at least Windows XP SP2, so you shouldn't try to install it with only Windows XP SP1 installed.

Thanks!

lagunalore:

hello, any solution to this problem?? I have windows XP and have tried installing with service pack 1 and 2, but i get the bootstrapper error...

You quoted the previous post but didn't add anything of your own.  Does that mean you are seeing the same error as well?  Can you please gather and post your call stack so we can try to narrow it down further?

You can also try to workaround this issue by installing the pieces of XNA Game Studio without running the bootstrapper.  You can find steps for how to do that in this blog post.

Thanks!

Hi, I got the same issue. Here is the error I get:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 136)
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
   --- End of inner exception stack trace ---
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
   at System.Configuration.ClientConfigurationSystem.PrepareClientConfigSystem(String sectionName)
   at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
   at System.Configuration.ConfigurationManager.GetSection(String sectionName)
   at System.Configuration.PrivilegedConfigurationManager.GetSection(String sectionName)
   at System.Diagnostics.DiagnosticsConfiguration.GetConfigSection()
   at System.Diagnostics.DiagnosticsConfiguration.Initialize()
   at System.Diagnostics.DiagnosticsConfiguration.get_IndentSize()
   at System.Diagnostics.TraceInternal.InitializeSettings()
   at System.Diagnostics.TraceInternal.get_Listeners()
   at System.Diagnostics.Trace.get_Listeners()
   at Microsoft.Xna.TaskManagement.Common.Support.Init()
   at Microsoft.Xna.TaskManagement.Common.Support.TrVerbose(String format, Object[] parms)
   at Microsoft.Xna.TaskManagement.TaskScheduler.Load(String fileName)
   at Bootstrapper.MaintenanceProgressPage.SetCurrentPage()
   at Bootstrapper.UninstallWizard.nextButton_Click(Object sender, EventArgs e)
   at Bootstrapper.UninstallWizard.removeButton_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Bootstrapper
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.11010.0
    CodeBase: file:///c:/1e833a3af397ad3d683ba9d4ccee10/Bootstrapper.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

This call stack means that there is something wrong with the .NET Framework 2.0 on your system (specifically, in the file c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config).

What OS are you running?  If it is an OS earlier than Windows Vista, you should be able to fully uninstall the .NET Framework 3.5 (if you have it), 3.0 (if you have it), then 2.0, and then re-install the .NET Framework 3.5 SP1 (which will install 2.0 and 3.0 back for you behind the scenes) in order to fix this.

If it is Vista or higher, it is a bit trickier because the .NET Framework 2.0 is an OS component on Vista and you cannot uninstall it or repair it without repairing the entire OS.  In that case, you can try something like the following to fix this:

1. Go to the folder c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config
2. Rename machine.config to machine.config.old
3. Make a copy of the file machine.config.default and rename the new copy to machine.config (keep the file machine.config.default there too in case you need it later)
4. Restart your computer
5. Try to install XNA Game Studio again

Hopefully one of these will help you in this scenario.

Thanks!

I'd like to add my 2 cents to this conversation since i just spent a week trying to work through the update issues with xna 3.1.  I've seen this problem since the 3.0 install so i had some idea of the problem - but i wanted to confirm they were the same.

    1.    I believe this issue has nothing to do with a machine or its configuration 
            - nor does it have to do with the actually installer/bootstrap.

    2.    The problem, for me, begins during the uninstall - i just don't know it :)
            - in certain instances, if you uninstall xna 3.0 or 3.1 with a profile that did NOT install xna,
                 (or not using the Administrator account - i'm still not sure if thats related or not)
              the uninstaller will leave behind Keys in the MSI hive of the registry where it installed the component records.
            - These keys are also LOCKED from every user and only the owner (SYSTEM) account can even access them.

    3.     When the new setup comes along - these keys for common MSI components are still in the registry and are locked.
            - Nothing the bootstrapper can do will fix this.
            - Neither will any kind of uninstall or CCleaner (i've even tried various registry cleaning apps).

    These keys are all located here:
        HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\[Profile ID]\Components

    I discovered this by breaking out the the MSI's from the packaged exe - then using: MSIEXEC /a XNA*.msi /l * mylog.txt
        the log shows the MSI failing on the removal of the old component keys to upgrade to the new versions (i think).

    I'm almost positive this is caused by only 1 of the sub-packages (xnags_platform_tools.msi) but i could be wrong since i've had this issue many times on at least 3 different pc's.

        All my pcs have these things in common:

                1.    All running some version of Vista (usually ultimate or business) or Server 2008

                2.    All have some form of Admin account other than the Administrator local admin account.

                3.    All have P4 >2g and atleast 2 g of RAM

                4.    Usually when i clean off a machine with a fresh install of windows - i setup everything up with Administrator
                           - then I create another account (root) and add this to the Administrators group
                              Later when i'm encounting this issue i've been using root - but i've tried to go back to Administrator & still encountered the same issue.

               
    Okay - if anything there made since - I hope its usfull.
            - Here is my theory - When the installer (or uninstaller) is removing the registry keys - it first removes the ACL accounts then tries to delete the key...
            This is then not possible since the installer no longer has rights to even read those keys.

    If the installer would either forceably clean all registry w/o chaning the ACL - this issue would probably never arise.  
        As it is now - the only way around this - without formatting the computer - is to install this sub package and everytime is crashes look at the id
         (something like Components\01598BAFE75148041BBA4C8C5E8ED356\9C2E753CF19021B4BBC1E2B79111B24C)
        Then i would search my registry for 01598BAFE75148041BBA4C8C5E8ED356 and delete it (ONLY DO THIS IF YOU KNOW WHAT YOU ARE DOING)!
            before i can delete it though - i have to reclaim ownership by Right Click\Permissions\Advanced\Owner\And adding my admin account back as Owner with full rights.
    Then I run the setup again - and it will give me another id...

After repeating this step a dozen times - I've usually had success in installing this sub package - then I can usually go back and run the EXE again with issue.

Hope this helps - 

(HUMAN)



    

I haven't heard of any specific cases of XNA Game Studio setup or any of its sub-packages causing this type of issue.  All of the XNA Game Studio sub-packages are MSIs, so Windows Installer controls the install and uninstall behavior.  Can you post the log files that you have from a failing uninstall on a file server so we could take a look?

I have heard of one case where the ACLs on some specific sub-keys in the registry can get set incorrectly such that only the SYSTEM account has permissions to the sub-key.  This scenario is described in more detail in the blog post at http://www.brianpeek.com/blog/archive/2007/11/29/weird-vista-registry-issue.aspx, and I have only heard of it affecting Windows Vista and higher so far.  Something causes the root key to have a completely blank ACL, then when Windows Installer adds registry keys/values under that key that has a blank ACL, the ACL gets set to grant permissions to the account that Windows Installer is running under (which is the local SYSTEM account).  My understanding is that Windows Installer uses standard registry APIs in these cases, and it doesn't specifically set ACLs itself.  When you add one account to an ACL that was previously blank, the ACL then restricts permissions to only that one account.  By default, the Administrators group should also have full control of HKLM, and the Users group should have read access.  The workaround in that blog post might help in this type of scenario.

Also, please note that the issues you describe are different than the callstack in the previous customer's post.  That call stack specifically shows a problem with some of the data in the file machine.config that is used by the .NET Framework 2.0 that is interfering with the ability to run WinForms code on that system.

Thanks!

I have the same problem. Although I am running Windows XP sp3. I have previously experienced difficultys while trying to open .msi-installfiles. I have tried unregging/reregging msiexec on my computer but it didn't solve the error.
I chose to debug in Visual Studio 2008 ( the full version) and It says "ArgumentException unhandled: Font Tahoma does not support style 'regular'". The error, as said before is in System.drawing.
Please help! I need to get XNA to work, in order to complete my studies.

It sounds like there is something wrong with the Tahoma font on your system and that is causing WinForms applications to not be able to work correctly if they use that font (like the XNA Game Studio installer does).  There are a couple of options that may help you here:

1. Go to %windir%\Fonts, find the file Tahoma.ttf, copy it to another directory on your computer, then right-click on it and choose Install.  This will hopefully re-install the Tahoma font so you won't hit this error anymore.
2. If the above doesn't work, you can use the steps listed at http://blogs.msdn.com/astebner/archive/2009/06/12/9740290.aspx to manually install the pieces of XNA Game Studio without needing to use the bootstrapper.exe package.  That won't fix the underlying problem with the Tahoma font on your system, but should allow you to avoid hitting that error during XNA Game Studio setup.

Thanks!

Hi I have this BOOTSTRAPPER ISSUE while in the middle of installing xna 3.1.  I tryed to do the workaround steps u posted from that other blog but got stuck at step 2 when I put xnags31_setup.exe/x in the run cammand box I also tryed xnags30_setup.exe/x just in case but got the same massage that it couldn't be found.

I would post this call stack u asked for in a latter post but I dont know how to do that?

The command line needs to have a space between the .exe and the /x.  It should look like this:

xnags31_setup.exe /x

Can you double-check that you are typing it exactly like this?  If you still get an error, can you please post a screenshot of exactly what you are typing when you try this?

Thanks!

This is exactly what I typed - xnags31_setup.exe /x

and I know i have it saved on my system.

And im typing this in the main Run command box just to clarify.

Would post a screen but this is a new labtop and dont exactly know how to since theres no print screen button.