Game Version: NWN 2 1.23.1765 (Platinum Edition)
Game Language: English
Retail or Digital: Direct 2 Drive
Processor Manufacturer: Intel
Processor Type: Core 2 Duo
Processor Speed: 2.0 GHz
Operating System / Service Pack: WindowsXP/SP3
System RAM: 2 gigs
Video Card Manufacturer: NVIDIA
Video Card Model: Geforce 7900 GTX
Video Card RAM: 512 megs
Video Card Driver Version: 270.61
Sound Card Manufacturer: Realtek
Sound Card Model: SB XFi or whatever applies for your sound card
DVD Type: DVD/ROM
Free Disk Space: C/15GB
D/10GB
Description: When starting up the Toolset i get a Windows error message:
"EventType : clr20r3 P1 : nwn2toolsetlauncher.exe P2 : 1.0.23.1765
P3 : 4a89fba1 P4 : nwn2toolset P5 : 1.0.1765.0 P6 : 4a89fc8c
P7 : 42ce P8 : 0 P9 : system.typeinitialization "
I am able to debug the file using Visual Studio (don't ask me why i have this installed) and it tells me that it throws a system.typeinitialization exception due to some conflict in the NWN2Toolset.dll .
I have all .NET Frameworks installed so therein should not lie the problem.
Direct X 9.0c is also installed.
So i have no clue what is causing the problem. Any help would be apprediated.
Thanks in advance.
Toolset Trouble
Débuté par
Fatboy85
, oct. 04 2011 06:16
Retour en haut
#2
Posté 04 octobre 2011 - 06:49
dunniteowl
-
- Members
- 1 559 messages
Is this a desktop or laptop model?
Also, it has been known to have issues at times with running the toolset on the steam version (don't have a good answer for you there) and sometimes, just sometimes, an attempt to install the .Net Framework from the support files in your Steam files might make everything okay fine. I know, I know, I read that you have .net installed, but sometimes, for whatever odd reason, some of the .net bells and whistles the toolset needs don't get activated during installation with later models of .net from the ,net version available at the original release and development of the game -- go figure.
As an anecdote, I literally went back and forth with one person about two years ago, repeatedly asking them to attempt to reinstall .net and he kept saying, "DAMNIT! I have it installed already!!"
I gave up and about a week later I got a PM. Short story, he apologized for getting so upset -- and, egg on face, yep, an attempt to reinstall (which didn't even go through) allowed the game to run.
Moral of the story: Sometimes, assuming everything is okay, because you have everything you're supposed to have on your system is not always the wisest course of action. And occasionally, what sounds like stupid advice actually isn't (though we should bear in mind that most stupid sounding ideas and advice really is just that. You also have to consider the source.)
regards,
dunniteowl
Also, it has been known to have issues at times with running the toolset on the steam version (don't have a good answer for you there) and sometimes, just sometimes, an attempt to install the .Net Framework from the support files in your Steam files might make everything okay fine. I know, I know, I read that you have .net installed, but sometimes, for whatever odd reason, some of the .net bells and whistles the toolset needs don't get activated during installation with later models of .net from the ,net version available at the original release and development of the game -- go figure.
As an anecdote, I literally went back and forth with one person about two years ago, repeatedly asking them to attempt to reinstall .net and he kept saying, "DAMNIT! I have it installed already!!"
I gave up and about a week later I got a PM. Short story, he apologized for getting so upset -- and, egg on face, yep, an attempt to reinstall (which didn't even go through) allowed the game to run.
Moral of the story: Sometimes, assuming everything is okay, because you have everything you're supposed to have on your system is not always the wisest course of action. And occasionally, what sounds like stupid advice actually isn't (though we should bear in mind that most stupid sounding ideas and advice really is just that. You also have to consider the source.)
regards,
dunniteowl
#3
Posté 04 octobre 2011 - 06:58
Fatboy85
-
- Members
- 5 messages
Well i already reinstalled all .Net Framework packs. Though not the the Steam one. I also have an old NWN 2 Dvd lying around somewhere ...
But i really don't want to reinstall it all (or parts of it) again cause it was a pretty big hassle the first time.
But i really don't want to reinstall it all (or parts of it) again cause it was a pretty big hassle the first time.
#4
Posté 04 octobre 2011 - 11:13
painofdungeoneternal
-
- Members
- 1 799 messages
From the description, ignoring what you have stated you have done, and just describing what possible causes there can be:
A. Missing .Net installation ( note there are versions 2.0, 3.5 or 4.0, and you have to have the actual version that is designed for the game installed, i think i've got all 3 since they are needed for multiple reasons beyond nwn2. Not even sure off the top of my head the version the game uses. ) Googling your specific error message seemed like about half the time this is the issue.
B. Messed up resources the toolset is loading, from the description it does not sound like this is the issue, as it usually indicates the file name it's getting hung up on.
C. Messed up Toolset preferences. Deleting them might fix it. There is some configuration choices, such as choosing a staging folder across a network that does not exist when starting prevents you from launching toolset. ( not sure where they are located off the top of my head, but you can probably find that via googling how to reset your nwn2 toolset preferences )
D. An actual program error, again googling brought that up as a possible cause of the error, but if that were the case it would mean the toolset would not start for a lot of other users.
E. Minor Corruption in toolset application causing D. above, perhaps due to virus or even some crack cd check remover ran by an end user, or just random disk errors messing up files. Basically you would need to reinstall the game, then patch from 1.20 to 1.23.
What is the actual issue, i'd say you should review the above list. The problem is almost always missing .Net files in my experience, but if you've ruled that out i am really moving from answers to guessing. I know far more about working with the toolset than fixing it, and can only hope you can figure out how to solve it via trial and error, wish i had a more specific answer.
A. Missing .Net installation ( note there are versions 2.0, 3.5 or 4.0, and you have to have the actual version that is designed for the game installed, i think i've got all 3 since they are needed for multiple reasons beyond nwn2. Not even sure off the top of my head the version the game uses. ) Googling your specific error message seemed like about half the time this is the issue.
B. Messed up resources the toolset is loading, from the description it does not sound like this is the issue, as it usually indicates the file name it's getting hung up on.
C. Messed up Toolset preferences. Deleting them might fix it. There is some configuration choices, such as choosing a staging folder across a network that does not exist when starting prevents you from launching toolset. ( not sure where they are located off the top of my head, but you can probably find that via googling how to reset your nwn2 toolset preferences )
D. An actual program error, again googling brought that up as a possible cause of the error, but if that were the case it would mean the toolset would not start for a lot of other users.
E. Minor Corruption in toolset application causing D. above, perhaps due to virus or even some crack cd check remover ran by an end user, or just random disk errors messing up files. Basically you would need to reinstall the game, then patch from 1.20 to 1.23.
What is the actual issue, i'd say you should review the above list. The problem is almost always missing .Net files in my experience, but if you've ruled that out i am really moving from answers to guessing. I know far more about working with the toolset than fixing it, and can only hope you can figure out how to solve it via trial and error, wish i had a more specific answer.
