i have just installed the .net 3.0 June CTP.I used to have a ball with .net run time components with beta 2 esp with CardSpace
now with June CTP i am getting the following error when
Event Type: Error
Event Source: Microsoft.InfoCards.Diagnostics 3.0.0.0
Event Category: System Event
Event ID: 102
Date: 13/07/2006
Time: 04:55:29
User: NT AUTHORITY\SYSTEM
Computer: xxxxxxxxx
Description:
Invoked FailFast
Message: The InfoCard Service cannot be started on this file system.
Stack Trace: at
System.ServiceModel.Diagnostics.ExceptionUtility.TraceFailFast(String message, EventLogger logger)
at System.ServiceModel.Diagnostics.ExceptionUtility.TraceFailFast(String message)
at Microsoft.InfoCards.Diagnostics.DiagnosticUtility.FailFast(String message)
at Microsoft.InfoCards.Diagnostics.InfoCardTrace.FailFast(String message)
at Microsoft.InfoCards.InfoCardService.FailFastIfNoFileSystemSecurity()
at Microsoft.InfoCards.InfoCardService..ctor()
at wmain()
at _wmainCRTStartup()
Process Name: infocard
Process ID: 236

Digital Identity Applet window cannot be opened
DiamonDogX
At the present moment reinstalling is not an option for me.
I just hope in the final release of CardSpace .Everything would be taken care of .!!!!!
Wondering if any one else had this problem when unistalling win fx runtime beta 2 to June CTP
DonRajah
Cheryl Hu
The file system on my machine is NTFS and still the digital identity selector applet/window does not apprear on my computer running windows XP. PLease help me ASAP.
Thanks in advance,
Shashi
Ayaz Virani
Hi guys,
I've been investigating this same error for somebody else (who was definitely using the July CTP) and I think I know what the problem is.
It turns out that you can only install CardSpace on NTFS. I'll bet your C: drive is FAT32. In this case the issue is compatibility.
Sorry to be the bearer of bad news, let me know if your filesystem data disproves my theory.
Pamela
turczytj
update
when i checked net start i dont have infocard service at all on my system
The service name is invalid.
EXPLANATION
You tried to start a service that is not configured on this system.
Is there any one who has gone through the same problem from upgrading WinFX Runtime components beta 2 to June CTP
I have found an reply when some one upgraded Jan CTP to Feb CTP
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=289671&SiteID=1
cheers
DonRajah
GLutz78
when i first came upon the July CTP i,the first thing i did was to installthe JULY CTP...the same probs as it was in the June CTP(the digital identity applet window cannot be opened).Well yes you are right the drive is on FAT 32 and not on NTFS.
Can anyone from the Windows CardSpace team confirm this...
thanx
Donrajah
tonn
stallion_alpa
Thanks
Donrajah
chaza
Hi,
hard to solve but I suggest to try:
Cancel all infocard* related procecces with Task Manager
If you try to open Card Selector via browser control be sure to import the related cerfiticate into "Trusted People" Store of the User.
I had some isssues too. On my opinion the best and cleanest way to use June CTP is to work on a clean installation of WinXP SP 2 Virtual Machine.
There are some propblems with the WinFX Beta 2 remove tool, so I think maybe there are some pieces of WinFX Beta 2 on your system (mainly WCF and WF).
Enjoy
Chris
Cavetroll
Hi,
I had some problems, too. On my opionion the best way is to install on a clean xp sp2. I think there are some problems with the remove tool.
If you want to try:
Repair your Beta 2 inistallation. Download the remove tool http://www.microsoft.com/downloads/details.aspx FamilyID=AAE7FC63-D405-4E13-909F-E85AA9E66146&displaylang=en and try to install .net 3 June CTP.
If this do not work you should not spend to much time to find the secretes (e.g. trash in the registry), just install on a clean system.
Bye
Chris
BlackMan890
Hey Shashi. Have you installed .NET Framework 3.0 on your XP machinesteveareno
YES. I will confirm that.
FAT32 will not work for CardSpace. The identity store for CardSpace must be on a volume that can be ACL'd to prevent processes from accessing the files.
I'm posting a blog entry right now, and I'll add that into the conceptual documentation in the SDK.
g
Garrett Serack | Program Manager |Federated Identity Team | Microsoft Corporation
blog:http://blogs.msdn.com/garretts
MillaT
That may have been a bug that was fixed in the later build.
G