• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Trouble with <expletive deleted> FSX SDK tools

spotlope

spotlope

FSDevConf team
Messages
346
Country
portugal
I've been trying to get the new SDK patch/tools running on my development rig for a few days now. I guess it's time to raise the white flag and ask for help...

Whenever I run ConfigSDK.exe, it crashes immediately. The error report lists an error with the Dot Net 2.0 runtime. Here's the text:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 11/16/2006
Time: 9:09:55 AM
User: N/A
Computer: BWOMACK
Description:
Faulting application configsdk.exe, version 1.0.0.0, stamp 44f27aab, faulting module kernel32.dll, version 5.1.2600.2180, stamp 411096b4, debug? 0, fault address 0x0001eb33.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 63 00 6f 00 6e 00 .c.o.n.
0030: 66 00 69 00 67 00 73 00 f.i.g.s.
0038: 64 00 6b 00 2e 00 65 00 d.k...e.
0040: 78 00 65 00 20 00 31 00 x.e. .1.
0048: 2e 00 30 00 2e 00 30 00 ..0...0.
0050: 2e 00 30 00 20 00 34 00 ..0. .4.
0058: 34 00 66 00 32 00 37 00 4.f.2.7.
0060: 61 00 61 00 62 00 20 00 a.a.b. .
0068: 69 00 6e 00 20 00 6b 00 i.n. .k.
0070: 65 00 72 00 6e 00 65 00 e.r.n.e.
0078: 6c 00 33 00 32 00 2e 00 l.3.2...
0080: 64 00 6c 00 6c 00 20 00 d.l.l. .
0088: 35 00 2e 00 31 00 2e 00 5...1...
0090: 32 00 36 00 30 00 30 00 2.6.0.0.
0098: 2e 00 32 00 31 00 38 00 ..2.1.8.
00a0: 30 00 20 00 34 00 31 00 0. .4.1.
00a8: 31 00 30 00 39 00 36 00 1.0.9.6.
00b0: 62 00 34 00 20 00 66 00 b.4. .f.
00b8: 44 00 65 00 62 00 75 00 D.e.b.u.
00c0: 67 00 20 00 30 00 20 00 g. .0. .
00c8: 61 00 74 00 20 00 6f 00 a.t. .o.
00d0: 66 00 66 00 73 00 65 00 f.f.s.e.
00d8: 74 00 20 00 30 00 30 00 t. .0.0.
00e0: 30 00 31 00 65 00 62 00 0.1.e.b.
00e8: 33 00 33 00 0d 00 0a 00 3.3.....
​
This doesn't mean much to me, but I thought someone else here might have a clue. I've downloaded and installed the latest .Net 2.0 runtime (and no, it wasn't .Net 3.0 by mistake), and have torn .Net out and reinstalled twice. Same for the SDK patch. I get other errors when running the autogen annotator, but I figured that's because I haven't been able to configure the SDK yet. My SDK/FSX are on another drive besides C, so the way I figure it, configuration is mandatory. Any insight?

thanks,
 
Kernel32 fault from .NET can be a lot of things, so not a whole lot of help there. I'm thinking security, service pack, windows firewall or anti-virus issue - especially if you use a Symantec product - not that I'm blasting them in any way of course, just that this has a familiar ring to it with Norton stuff.

The good news is that I'm not the only one getting useless error messages :)

My usual troubleshooting routine involves a trip to EventViewer and a visit to WindowsUpdate.com to see if anything out there helps.

I assume you have FSX installed and activated on the system?

I doubt this is a framework install issue. A framework error in kernel32 or user32 indicates an underlying OS problem in most cases in my experience.

I apologize for not being terribly helpful, but hopefully something above is of assistance to you.

Regards,

Etienne
 
Thanks, Etienne. I'm not a believer in Norton, and have none of their products on my system. I'll try disabling my NOD32 antivirus to see if that changes anything. I think you're probably right that the problem lies somewhere deep in the system. I need to take a trip over to Windows Update and see if I can find any solutions.

thanks,
Bill
 
Do you get these kinds of errors when running any .NET based application, or just the ConfigSDK tool?
 
ryantrem said:
Do you get these kinds of errors when running any .NET based application, or just the ConfigSDK tool?
Click to expand...

Success! I finally uninstalled and reinstalled things in the right order. First, uninstalled the SDK (which didn't actually remove the SDK files), then deleted the SDK directory, then uninstalled .Net 2.0 per MS's instructions, then rebooted, resinstalled .Net, then the SDK. Now everything is working well again. I think being a beta tester kinda screwed things up, because there were old bits of code that weren't uninstalling properly. Thanks for the help!
 

Attachments

  • configSDK-error.jpg
    configSDK-error.jpg
    94.5 KB · Views: 467
Last edited:
Hi,

It is a security issue with the .NET framework. I spot in there "Strong name validation failed" for the zone "My Computer".

What else have you installed or configured on there?

.NET is unable to validate the strong name (a unique ID given to a binary at compile time to verify it is what it says it is and not an imposter). Because of that, .NET framework is unable to load the binary.

Best regards,
Robin.
 
No need for apology, Robin. I edited it once I figured out the problem. It was a call for help previously. Anyway, thanks for taking the time.
 
You must log in or register to reply here.
Back
Top