Home : Products : General : fixing svcutil.exe in Orcas Beta 2
Q10440 - FIX: fixing svcutil.exe in Orcas Beta 2

'svcutil.exe' assembly that ships with Orcas Beta 2 is "broken" - it is not signed.

Running it will result in the following error:

svcutil.exe has encountered a problem and needs to close....

WCF Test Client: Failed adding service./
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'svcutil, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
File name: 'svcutil, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
The Zone of the assembly that failed was:
MyComputer

 

This is a known issue - (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1932994&SiteID=1)

The fix is - navigate to the Windows SDK directory (e.g. C:\Program Files\Microsoft SDKs\Windows\v6.0a\bin) and run "sn -Vr svcutil.exe"

Related Articles
No Related Articles Available.

Article Attachments
No Attachments Available.

Related External Links
No Related Links Available.
Help us improve this article...
What did you think of this article?

poor 
1
2
3
4
5
6
7
8
9
10

 excellent
Tell us why you rated the content this way. (optional)
 
Approved Comments...
I ran the prompt and I stopped getting an error when I ran svcutil. Approved: 11/11/2007 3:40 PM
Please say that under Vista you need to start the command line prompt as Administrator. Approved: 9/16/2007 5:05 AM
Created on 8/10/2007 11:40 AM.
Last Modified on 8/10/2007 11:40 AM.
Last Modified by No Author Name Available!.
Article has been viewed 6121 times.
Rated 6 out of 10 based on 20 votes.
Print Article
Email Article