Skip to main content

Unsolved

This post is more than 5 years old

sysbr34kr

30 Posts

339558

June 1st, 2012 12:00

Alienware Command Center Error

I've reinstalled my Windows 7 OS and downloaded and installed the drivers on Dell support, after installing Alienware Command Center I've been getting this error message: 

System.NullReferenceException: Object reference not set to an instance of an object.
   at AlienLabs.ThermalControls.Domain.Profiles.Classes.ProfileRepositoryClass.get_IsManualFanSetting()
   at AlienLabs.ThermalControls.Controller.Classes.ProfileManagerClass.Init()
   at AlienLabs.ThermalControls.Controller.Main.processWindowsLoaded()
   at AlienLabs.ThermalControls.Controller.Main.Window_Loaded(Object sender, RoutedEventArgs e)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at MS.Internal.FrameworkObject.OnLoaded(RoutedEventArgs args)
   at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
   at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)
   at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

Can anyone give me some enlightenment?
PS: Excuse my English if I make any mistakes. 

 

Tesla1856

10 Wizard

 • 

17.8K Posts

 • 

71K Points

June 3rd, 2012 16:00

If the first procedure doesn't work, try this one:

Try 2 - Clean Installing MIO drivers and CC due to poor driver installer support and/or the fact that the MIO-Board hardware device never prompts for drivers or never shows yellow-error in Device Manager when core drivers are missing.

This procedure assumes that the MIO-Board tests good in Dell Diags (outside of Windows) and you can control the lights and fans INSIDE Dell Diags using their tests. However, when you properly install Command Center in Windows 7, you get strange .Net error messages and the sub-apps don’t operate properly. These error messages mean the Command Center software is still having trouble communicating with the MIO-Board.

If the MIO-Board tests FAIL in Dell Diagnostics, there is really no chance it will operate in Windows with Command Center software. The MIO-Board tests in Dell Diags have been known to reset it in some fashion. The Power Dissipation Fix has also been known to reset MIO-Boards, so be sure to try them both.

Note: Never use the Upgrade feature inside Command Center. Always, uninstall old, reboot, install new fresh. Never install older versions of Command Center on a machine. Always re-install the same version or newer.

Prerequisites:

- Be sure the ONLY USB devices connected to PC are a normal USB mouse and keyboard, (not any Alienware TactX models with lighting or that use AlienFX) plugged into ports on back of PC. Nothing else.
- Disable your Anti-Virus software (and be sure it stays disabled throughout the entire process and reboots)
- Microsoft Net 4.0 Client Framework is required for Command Center install. You can get it from Windows Update.
- Have Command Center downloaded and ready to install later.  A current, later release version is suggested… something around v2.6.17.0 or the new v2.7.x release (if that’s what you have been trying to use already). Do not install old v2.5.x versions (even if File Area suggests them to you).

Completely Uninstall Command Center.
Reboot and go back into Windows.

Delete folder c:\Program Files\Alienware
Delete folder c:\Users\YourName\My Documents\AlienFX

Go into Control Panel / User Accounts
Select "Manage Another Account"
Select "Create a New Account"
Enter a new name, and select "Administrator" as type
- Click "Create Account" button
- Follow prompts to create this new temporary user with Admin privileges

Close all windows and Shut-Down Windows (Power down machine)

Unplug the power cord from the back of your PC, then press and hold the power button down for 10 seconds to drain residual power from MIO board to further reset it and to insure a trouble-free CC install. Then, power back up.

Login to Windows with this new Account

Install the Command Center (for desktops) and reboot
Note: The first time a v2.6.x version (or higher) is installed on your machine, it will upgrade the MIO-Board's firmware to v2.x
Reboot if asked to.
Test operation of Command Center.

If it works, try rebooting and login again with new account. Test operation of Command Center again.

If it is still working, try rebooting and login with your normal (old) account. Test operation of Command Center.

You should now be able to delete the temporary account. Since changes to the machine were made with an Admin account, re-config should carry over to all users.

Good luck and report back if it worked. Also, if any steps are incorrect and need clarification, please let me know.

sysbr34kr

30 Posts

June 4th, 2012 14:00

Alright, got the keyboard and the mouse, but... How do I clean install the MIO board drivers? Can't seem to find anything relative to the MIO board drivers.

Tesla1856

10 Wizard

 • 

17.8K Posts

 • 

71K Points

June 4th, 2012 15:00

Alright, got the keyboard and the mouse, but... How do I clean install the MIO board drivers? Can't seem to find anything relative to the MIO board drivers.
 
Try the first procedure. If it doesn't work, try the second procedure I just posted. Dell has not provided a "clean install" procedure. The only thing I know to do is uninstall and reboot. Also, Procedure #2 post has some additional "cleaning" steps before full re-install. If the Registry or other part of Windows is corrupt, the new temp. Admin user creation procedure should help.
 
Because of :
poor driver installer .exe support and/or the fact that the MIO-Board hardware device never prompts for drivers or never shows yellow-error in Device Manager when core drivers are missing.
... it's impossible to do a traditional "cleaning first" to facilitate a true "clean install".
Alienware would have to provide a document (or app that does it) that describes all the files and Registry settings that need to be removed. I've never seen such a thing.
 
EDIT: MIO-Board drivers and Services are inside the Command Center installer.

sysbr34kr

30 Posts

June 4th, 2012 17:00

No change, tried both procidures.

Tesla1856

10 Wizard

 • 

17.8K Posts

 • 

71K Points

June 4th, 2012 18:00

No change, tried both procidures.
 
Ok, so we move on.
 
Backup any important data files (there really shouldn't be any new ones yet ... you should still have your last backup).
 
Still using just generic keyboard and mouse (connected to back).
 
Test MIO-Board in Dell Diags again to make sure it's still working.
 
Shut-Down/Turn off and do Power Dissipation Fix to ready MIO-Board.
 
Clean install Windows 7 and install drivers in proper order:
 
 
Don't worry, it will go fast.
 

sysbr34kr

30 Posts

June 4th, 2012 18:00

Alright, I'll let you know tomorrow.

sysbr34kr

30 Posts

June 6th, 2012 02:00

Ok, I could not remove the power cable from the MIO board, even if my life depended on it. It's like it's binded by magic or something... Is there any other end I can disable the MIO board, preferably one that allows me to keep the skin on my fingers? (starting to hate that MIO board right now)

Tesla1856

10 Wizard

 • 

17.8K Posts

 • 

71K Points

June 6th, 2012 12:00

The instruction say to remove the MIO-Board communication cable from USB1 at the motherboard. The MIO-Board POWER cable stays connected.

If you want, you can skip that step.

sysbr34kr

30 Posts

June 6th, 2012 18:00

Oh, right... But I have no ideia which one is the USB1, any reference?

sysbr34kr

30 Posts

June 6th, 2012 19:00

Alright then. I'll inform you later.

Tesla1856

10 Wizard

 • 

17.8K Posts

 • 

71K Points

June 6th, 2012 19:00

Oh, right... But I have no ideia which one is the USB1, any reference?
 
It's in either Owner's Manual or Service Manual.
 
I'm sure it also says on the motherboard itself.
 
But really, skip disconnecting it. I put that in to help prevent MIO-Boards from getting mixed up. But since yours already is, I think it might be too late for you.

Tesla1856

10 Wizard

 • 

17.8K Posts

 • 

71K Points

June 6th, 2012 22:00

Surprisingly it worked! Everything is working correctly now, thanks a lot for you help Tesla.

 
I thought it might ( I was hoping anyway).
 
Glad to hear it. You are welcome.
 
You are the second person recently, who:
 
- Command Center and MIO-Board are working fine
- Clean installed Windows-7 (for other reasons)
or
- Accidentally used the "Upgrade" feature inside Command Center.
 
and then ...
- Command Center couldn't communicate with the MIO-Board any more
- MIO-Board still tested good in Dell Diags (outside of Windows)
- No amount of proper Command Center un-installs/re-installs, reboots, or hacking/cleaning could fix it.
 
The fix is apparently to just go ahead and ...
- Clean install Win-7 completely (or over again a second time)  ... and then it works fine.
 
IIRC, users have reported this scenario many times over the years. At least now we know a fix. In that capacity, you followed directions properly and helped a lot yourself.
 
To others reading this thread later, remember, this fix is only sure to work when...
- MIO-Board still tests good in Dell Diags (outside of Windows)
 
 

sysbr34kr

30 Posts

June 6th, 2012 22:00

Surprisingly it worked! Everything is working correctly now, thanks a lot for you help Tesla.

MrSinatra

1 Rookie

 • 

22 Posts

March 5th, 2013 00:00

also, i just noticed something else...

where you download this stuff, i see two files, the original A00 release:

2.6.8.0

and the one i am trying to install above that won't work, A01:

2.8.8.0

which is dated 2/22/2013.

but "in" that one there are "previous versions" and one of them is:

2.8.10.0

and in my exp the "10" is ten, and also it is dated 2/22/2013 and marked A02!

and there are some other strange versions as well.

regardless, it failed too.

MrSinatra

1 Rookie

 • 

22 Posts

March 5th, 2013 00:00

hi,

i thought this might be a good thread to reply in, as people here seem to know things!

i have a M14x (R1) and it had Alienware Command Center on it.  at some point it updated from within the program, but it still mostly worked, until recently, when it no longer did.  i then uninstalled it completely, (well, dell support did), and now it won't install.  

i was so frustrated i got a SSD and installed windows 7 64 with all updates tonight.  guess what?  2.8.8.0 STILL won't install!  UGH!

if anyone can help i'd really appreciate it, here is the LOG:

਍਍[03/05/13 02:38:40] Update Package Execution Started
[03/05/13 02:38:40] Original command line: "C:\Users\MrSinatra\Downloads\AlienCC Application_8D9J2_WN_2.8.8.0_A01.EXE" 
[03/05/13 02:38:40] DUP Framework EXE Version: 3.0.93.1
[03/05/13 02:38:40] DUP Release: 8D9J2X00-00
[03/05/13 02:38:40] Intializing framework...
[03/05/13 02:38:40] Server Infastructure Detected...Proceeding with PM Module...
[03/05/13 02:38:40] Querying if HAPI is Installated...
[03/05/13 02:38:40] HAPI is not present in the System, Preparing to Install HAPI...
[03/05/13 02:38:40] Creating Temp Directory to Extract HAPI.
[03/05/13 02:38:40] Temp Directory for HAPI Extraction created Successfully at :C:\Windows\temp\{95B716FB-A30C-426B-8371-3716F3B8819F}
[03/05/13 02:38:40] Extracting HAPI from Resource at:C:\Windows\temp\{95B716FB-A30C-426B-8371-3716F3B8819F}
[03/05/13 02:38:40] HAPI Extracted Successfully from Resource at:C:\Windows\temp\{95B716FB-A30C-426B-8371-3716F3B8819F}
[03/05/13 02:38:40] Preparing path to Unzip HAPI Installer from HAPI.zip 
[03/05/13 02:38:40] HAPI Installer Successfully Unzipped to HAPI folder, from HAPI.zip at:C:\Windows\temp\{95B716FB-A30C-426B-8371-3716F3B8819F}
[03/05/13 02:38:40] Before Installing HAPI, Checking if HAPI Installation is in Progress Via Other Instance
[03/05/13 02:38:40] No Concurrent Instance of HAPI Installation is in progress OR  HAPI is getting installed for the First time.
[03/05/13 02:38:40] Preparing to Install HAPI
[03/05/13 02:38:46] weInstallHAPI=true & HAPI Installated SuccessFully.
[03/05/13 02:38:46] Querying Personality Module for data via ..GetPersonalityInfo()
[03/05/13 02:38:46] Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()
[03/05/13 02:38:46] Failed to obtain Personality Information
[03/05/13 02:38:46] ...WARNING...Personality Module lib FAILED to return Values via ..GetPersonalityInfo().
[03/05/13 02:38:46] logo.png
[03/05/13 02:38:49] User Command: attended
[03/05/13 02:38:49] DUP Capabilities Value: 44040191 (0x29FFFFF)
[03/05/13 02:38:49] DUP Vendor Software Version: 2.8.8.0
[03/05/13 02:38:49] Local System/Model Compatible with this Package? Yes
[03/05/13 02:38:49] Local System OS Version: 6.1.1.0
[03/05/13 02:38:49] OS Compatible with this Package? Yes
[03/05/13 02:38:49] Local System OS Language: EN
[03/05/13 02:38:49] Language Compatible with this Package? Yes
[03/05/13 02:38:50] Identified Behavior : attended
[03/05/13 02:38:50] Temporary payload log file name: C:\ProgramData\dell\drivers\AlienCC Application_8D9J2_WN_2.8.8.0_A01\DUPA044.tmp
[03/05/13 02:38:50] Translated Command Line : setup.exe /Verbose""C:\ProgramData\dell\drivers\AlienCC Application_8D9J2_WN_2.8.8.0_A01\DUPA044.tmp""
[03/05/13 02:38:50] Path : C:\ProgramData\dell\drivers\AlienCC Application_8D9J2_WN_2.8.8.0_A01
[03/05/13 02:38:50] Identified Behavior : attended
[03/05/13 02:38:55] Append Vendor Software Log: C:\ProgramData\dell\drivers\AlienCC Application_8D9J2_WN_2.8.8.0_A01\DUPA044.tmp
[03/05/13 02:38:55] 
--- Start of Vendor Software Log ---
 
[03/05/13 02:38:55] 
--- End of Vendor Software Log ---
 
[03/05/13 02:38:55] Vendor Software Return Code: 1203
[03/05/13 02:38:55] logo.png
[03/05/13 02:38:56] Name of Exit Code: UNKNOWN_OPTION
[03/05/13 02:38:56] Exit Code set to: 11 (0xB)
[03/05/13 02:38:56] Result: FAILURE
[03/05/13 02:38:58] Open file: C:\ProgramData\Dell\UpdatePackage\Log\AlienCC Application_8D9J2_WN_2.8.8.0_A01.txt

Was this post helpful?

View All

No Events found!

Top