Unsolved
This post is more than 5 years old
1 Message
0
84239
August 16th, 2008 14:00
"Problem Applying Profile" message with Intel Proset wireless
Hi, I'm wondering if someone can tell me how to fix this. My wireless is not working. Every time I try to connect, I get a message that says "Problem Applying Profile." I ran the diagnostic tests and it failed the "Association test" but I cannot figure out how I am supposed to fix it. Thanks.
No Events found!
volcano11
2 Intern
•
28K Posts
0
August 16th, 2008 15:00
You probably need to delete the Profile in the Intel ProSet Utility and re-create it. You can also see if it works if you let Windows manage your wireless networks by opening the Intenret ProSet Utility and unchecking the box next to "Let this Utility Manage..."
Steve
DFO1201
6 Posts
0
September 7th, 2008 20:00
Here's what worked for me. Good Luck!
Many times when starting up, the Intel Proset Wireless application did not automatically connect to my default profile. When I attempted to manually connect, it issued message "Problem Applying Profile!". I would need to reboot or disable/enable the wireless device to get it to work. The Windows-provided application never had this problem.
I used the Proset Wireless troubleshooter (Tools -> Intel(R) Wireless Troubleshooter...), clicked on Wireless Event Viewer, clicked "Save As...", clicked "Save" to save the trace data into a CSV file. The trace showed that I was fighting with the SYSTEM process to get the adapter port. When I got it first, everything was fine. The problem was when SYSTEM got it first:
Source Domain User Description
Dot1XConfig Security SYSTEM Xixa successfully attached to port...
Dot1XConfig Security SYSTEM Stopped.
Dot1XConfig Security usera Initialization- new adapter (MAC=...
Dot1XConfig Security usera Xixa FAILED attaching to port...(error=-20)!
Muroc Api General usera Profile xxxx for xxxx being applied.
Dot1XConfig Security usera StopAuthentication- adapter context is NULL!
The solution seemed to be to prevent SYSTEM from trying to get the port. Dell and Intel support provided the canned responses and did not look at the trace data and did not resolve the problem.
I eventually found a way to fix this. I needed to change the Dot1xCfg DCOM object so that SYSTEM could not launch the application. This worked on XP Home.
Click Start, Run, enter dcomcnfg. You may get a Firewall warning; I said "ask me later".
Click Component Services, Computers, My Computer, DCOM Config. I got a warning and replied "NO".
Find Dot1xCfg, right click, click Properties.
Click the Security tab, under Launch and Activation Permissions, select Customize and click "Edit".
If SYSTEM is there, select it and set all permissions to "Deny". If not there, it may be getting permission through a group, so click "Add..." and add SYSTEM and set all permissions to "Deny".
After you do this and reboot, you should connect every time.