|
|
Task Board for Team System Beta Discussions (Read Only)
Started by Crispin Parker at 09-25-2008 11:34 AM. Topic has 24 replies.
 
 
|
|
Sort Posts:
|
|
|
|
09-25-2008, 11:34 AM
|
Crispin Parker
Joined on 11-13-2007
Posts 695
|
Beta 3 - Provider load failure
|
|
|
|
|
Hello,
Two Beta 3 Task Board users have reported an error "Provider load failure". If you are experiencing this issue please post below so that we can judge the size of the problem.
Kind Regards,
Crispin Parker, Technical Consultant, Conchango.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
09-26-2008, 10:19 AM
|
Kabwla
Joined on 07-28-2008
Culemborg - Netherlands
Posts 105
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
Crispin send me this:
Looks like the assembly problem may be a “Microsoft 3.5” feature: http://msdn.microsoft.com/en-us/library/bb961987.aspx
I have not been able to perform this test at the moment because of time contsrictions, if anyone could report their findings?
"Anything one man can imagine, other men can make real." - Jules Verne.
|
|
|
|
|
Report
|
|
|
|
11-05-2008, 4:41 PM
|
dboucher
Joined on 11-05-2008
Denver, CO
Posts 7
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
Every time I launch Task Board, I get an unhandled exception error: System.Reflection.TargetInvocationException Provider load failure Ignore/Continue
I tried going to http://msdn.microsoft.com/en-us/library/bb961987.aspx to register the System.Management.Instrumentation dll. One item of note, using the VS2008 command prompt on Windows XP, you need to enter the short path (i.e. regasm C:\PROGRA~1\REFERE~1\MICROS~1\FRAMEW~1\v3.5\SY5599~1.DLL). That worked, but it did not solve the Provider load failure error.
Other thoughts?
|
|
|
|
|
Report
|
|
|
|
11-06-2008, 10:13 AM
|
Crispin Parker
Joined on 11-13-2007
Posts 695
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
Hi DBoucher,
Sorry to say that I never got any feed back from users with this problem. My assumption was that the problem was caused by a particular .Net framework installation configuration, something like 3.5 and no 2. But as I cannot re-create the issue in our test platforms, it is impossible to know for sure.
This error has only been reported twice and the Task Board beta has over 1000 unique users, so the cause is likely to be quite obscure.
Does googling the "Provider load Failure" and the ".Net Management Assembly" error provide any new clues?
Regards,
Crispin Parker, Technical Consultant, Conchango.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
11-06-2008, 10:18 AM
|
Kabwla
Joined on 07-28-2008
Culemborg - Netherlands
Posts 105
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
I am sorry, We are completely swamped with work, and since we have machines that work fine, we never got around to testing the solution.
I am eagerly following this thread though.
"Anything one man can imagine, other men can make real." - Jules Verne.
|
|
|
|
|
Report
|
|
|
|
11-07-2008, 1:51 PM
|
ginmic
Joined on 03-06-2008
Posts 4
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
Hello there, I just want to provide some info about the occurency of this problem.
I am in charge of setting up the Task Board where I work and I have experienced two workstation/clients that has had this problem. I haven't looked in to it yet.
The outcome; the users simply can't use the task board :(
BR
Michael
|
|
|
|
|
Report
|
|
|
|
11-10-2008, 11:45 AM
|
Crispin Parker
Joined on 11-13-2007
Posts 695
|
|
|
Hello All,
I'm going to need some assistance with this one. I cannot re-create the issue on any of our test machines and no-one in our company has reported the issue either...
I'm working on the assumption that this problem is caused by the:
- Assembly: "System.Management.dll"
- Version: 2.0.50727.1433
- Installation Location: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
- Cause: In order for the TB app to identify the local network adaptor physical addresses (MAC Address) available on the system, the "System.Management.dll" assembly is used to query the systems variables:
Code:
var scope = new ManagementScope(String.Format(@"\\{0}\root\cimv2", Environment.MachineName)); var query = new ObjectQuery("SELECT MACAddress FROM Win32_NetworkAdapter"); var searcher = new ManagementObjectSearcher(scope, query); var addresses = searcher.Get().Cast<ManagementObject>() .Where(mo => mo["MACAddress"] != null) .Select(mo => mo["MACAddress"].ToString());
|
|
I have attached a command line test utility that executes the above code. Please can those affected, run the utility and post back there findings / error messages produced.
Remember, those who help in the beta testing will get discounts on the cost of the commerical TB release.
Regards,
Crispin Parker, Technical Consultant, Conchango.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
11-10-2008, 4:29 PM
|
dboucher
Joined on 11-05-2008
Denver, CO
Posts 7
|
|
|
Hi --
Thanks for your assistance with this!
When I run your utility from the command prompt, I get this error:
Unhandled Exception: System.Management.ManagementException: Provider load failure at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at System.Linq.Enumerable.<CastIterator>d__b0`1.MoveNext() at System.Linq.Enumerable.<WhereIterator>d__0`1.MoveNext() at System.Linq.Enumerable.<SelectIterator>d__d`2.MoveNext() at GetMacAddress.Program.Main(String[] args)
Also, it pops up a "Send to Microsoft" error. I took a screen shot of the contents of that error and attached it to this post.
Please let me know if you have any thoughts/suggestions. Thanks!
|
|
|
|
|
Report
|
|
|
|
11-10-2008, 6:17 PM
|
Crispin Parker
Joined on 11-13-2007
Posts 695
|
|
|
OK, having an error is good. At least we can re-create the problem.
Let's consider the environment:
- What is the OS?
- What versions of the .Net Framework are installed?
- What version of the "System.Managment.dll" is installed (location indicated in above post)?
A possible cause of this problem is that the "Terminal Services" windows service is not running. Ensure this service is running on the client machine.
I have attached another version of the test program that might give a little more error message detail. Run the new test program and post the resulting command line output. This version also looks for an explicit version of the assembly (v2.0.50727).
You may also try the test while running Filemon (http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx). This may highlight what files are missing.
Also, does the executing account have administator permission? If not, does running the test as an administrator fix the problem?
Crispin.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
11-11-2008, 9:18 AM
|
Crispin Parker
Joined on 11-13-2007
Posts 695
|
|
|
Testing the underlying WMI:
The "System.Managment.dll" .Net assembly provides a wrapper for the WMI (Windows Management Instrumentation) functionality. By following the below steps you can check the WMI works correctly when not accessed through the .Net Assembly:
- At the Run prompt, type: wbemtest.exe and hit return
- In the "Windows Management Instrumentation Tester" app, click Connect
- Type: root\cimv2 (in the first text box) and click Connect
- Click the Query button.
- Type:
SELECT * FROM Win32_NetworkAdapter WHERE MACAddress IS NOT NULL
- Click Apply
This should display a list of items like:
WiFi_NetworkAdaptor.DeviceID="1" Win32_NetworkAdaptor.DeviceID="2" Win32_NetworkAdaptor.DeviceID="10" ...
Double click on one of the listed items to see it's MACAddress. Hint: you'll have to scroll the propeties a little bit.
If this all works correctly, then the problem must be with the "System.Management.dll" assembly.
Please post your feedback and remember license discounts are on offer!
Regards,
Crispin Parker, Technical Consultant, Conchango.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
11-11-2008, 4:30 PM
|
dboucher
Joined on 11-05-2008
Denver, CO
Posts 7
|
|
|
Hi Crispin --
Many thanks for your attention to this issue. Very impressive.
Apologies for not responding yesterday. A bit of a crazy day.
To answer your questions: My OS is: Win XP Pro v 2002 sp 3 The following versions of the .NET Framework are currently installed on my system: .NET Compact Framework 1.0 SP3 Developer .NET Compact Framework 2.0 SP2 .NET Compact Framework 3.5
.NET Framework 1.1
.NET Framework 1.1 Hotfix (KB928366)
.NET Framework 2.0 SP1
.NET Framework 3.0 SP1
.NET Framework 3.5 Version of System.Management.dll: 2.0.50727.1433 Terminal Service is running.
I ran your updated test program and the output is: Provider load failure at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at System.Linq.Enumerable.<CastIterator>d__b0`1.MoveNext() at System.Linq.Enumerable.<WhereIterator>d__0`1.MoveNext() at System.Linq.Enumerable.<SelectIterator>d__d`2.MoveNext() at GetMacAddress.Program.Main() Process Complete. Press any key to exit...
I also ran your updated test program while FileMon was running. The output of that is found in the filemon_output.txt file contained in the test_results.zip file attached to this post.
I am an administrator of this machine, so that's not the issue.
Finally, I followed the instructions in your post above regarding testing the underlying WMI. At step 6 of your instructions, when I click "Apply", it throws the "Provider Load Failure" error again. A screen shot of that is found in the wmi_error_screen_shot.jpg file contained in the test_results.zip file attached to this post.
Thanks very much for your help with this.
-- Dave
|
|
|
|
|
Report
|
|
|
|
11-12-2008, 3:22 PM
|
Crispin Parker
Joined on 11-13-2007
Posts 695
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
Hi Dave,
Thanks for the feedback. From your responses it apears that the "System.Management.dll" is not the root cause of the problem.
The wbemtest.exe test utility deals directly with with the COM dlls in the system. So there must be a problem with them. Here are the main COM objects used:
fastprox.dll WMI Microsoft Corporation 5.01.2600.5512 C:\WINDOWS\system32\wbem\fastprox.dll wbemcomn.dll WMI Microsoft Corporation 5.01.2600.5512 C:\WINDOWS\System32\Wbem\wbemcomn.dll wbemprox.dll WMI Microsoft Corporation 5.01.2600.5512 C:\WINDOWS\system32\wbem\wbemprox.dll wbemsvc.dll WMI Microsoft Corporation 5.01.2600.5512 C:\WINDOWS\system32\wbem\wbemsvc.dll wbemtest.exe WMI Microsoft Corporation 5.01.2600.5512 C:\WINDOWS\System32\Wbem\wbemtest.exe WINMM.dll
I found this article in the Microsoft support web site that relates to .Net Framework Version 1.0 and 1.1. Not sure if this solution might also apply for your environment.
http://support.microsoft.com/kb/834536
I'm wondering if the .Net Framework installation sequence has caused this problem. Maybe installing 2.0 after installing 3.5 is causing the same problem as installing 1.0 after installing 1.1...
Crispin.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
11-12-2008, 3:53 PM
|
dboucher
Joined on 11-05-2008
Denver, CO
Posts 7
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
Hi Crispin --
Looking at that Microsoft site, I try to follow their instructions, however, the following registry entry does not exist on my machine: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Catalog42\NetFrameworkv1
There is no Catalog42 node.
So, unfortunately, I can't change any settings there.
Thoughts?
|
|
|
|
|
Report
|
|
|
|
11-13-2008, 12:14 PM
|
Moltas
Joined on 09-16-2008
Sweden
Posts 6
|
Sv: Re: Beta 3 - Provider load failure
|
|
|
|
|
It works for me.
I have VMWare Workstation installed and the app returns all NICs including them.
|
|
|
|
|
Report
|
|
|
|
11-13-2008, 12:43 PM
|
Crispin Parker
Joined on 11-13-2007
Posts 695
|
Re: Beta 3 - Provider load failure
|
|
|
|
|
A little more research has turned up that you can re-register the WMI providers by following the below:
- Launch a command prompt (use an elevated prompt if running vista)
- Type: CD "c:\windows\system32\wbem" and hit return.
Note: Adjust system folder location if running windows server.
- Type: for /f %s in ('dir /b *.mof *.mfl')do mofcomp %s and hit return.
This command will cycle through and re-register all the "mof" and "mfl" files in the current directory. Once the process completes, run the wbemtest.exe application again and check if the Mac Address query (detailed in above post) works.
Please post back your findings.
Crispin.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
|
|
Page 1 of 2 (25 items)
|
1 2 > |
|
|
|
Scrum for Team ... » Task Board for ... » Task Board for ... » Beta 3 - Provider load failure
|
|
|
|