This application has failed to start because the application configuration is

Newbie Spellweaver
Joined
Jul 4, 2007
Messages
23
Reaction score
0
Hi Guys,

i have the ascent 3.5 stable and i can play very well... But now i would like update my version to someone of Kameleon20 Post.

I have downloaded the 3945 version and when i execute the ascent-world.exe file i got this error:

"This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem"

What can i do?... I have read in another post where somebody sayed if i was administrator but this not solve the problem...

The 3_8 version doesn`t work to me and i got the same error...
I can't execute logonserver.exe or ascent-world.exe...
 
thanks dwolf312 for your fast answer...

I have download the same version from djaligators and i have got the same error:

"This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem"

thats message appear when i execute the ascent-world.exe or ascent-logonserver.exe files... I can't do nothing else....
the console window doesn't appear.... And this it's happen with 38XX versions!! Al 38XX and 39XX versions.... Why?

The 3_5 version works fine.... and i have configurated the .conf files correctly... Maybe i have to do something else?....

Please Heeelp me!!!
 
That's a work around, however not really a solution...

The reason you get that error is because it's been compiled with MS VC++ 2008, which requires .NET Framework 3.5...

Alot of people build Ascent using VC++ 2008, therefore your best solution is to install .NET 3.5, that way you can use anybodies build ;)
Unless you happen to download one of the few who use VC++ 2003 or earlier...
 
Ahhhh.. .Ok guys... thank you very much!!

I'm going to download the 3.5 framework and install it... But, Only one question:

The 3945 (NCDB 1105) is better than the 3.5 stable version (NCDB 1092)?
I have been playing with 3.5 and i know what bugs it has....

Do you know if 3945 version works fine with collision.dll and vmaps?
Can i play in a Stockade Stance with prisioners without cross the walls and kick me since another room?
 
I haven't done much testing of vmaps... I should go into stockade and test it.
However there is only one way to find out!
Make a backup first and if it doesn't work you can always roll back to 3.5 stable...

I'm sure 3.8 stable will be an improvement though

edit: actually i'll go test stockade now. lol
 
MMm.. no daedelus82,

i think that the version is not stable.... Maybe we should be wait for next updates....
What stable version do you have?... Could you tell me some version better than 3.5?

Some version without crashes.... please..jeje...
 
I've used a number of stable releases from 3800'ish up to 3936 which was released earlier today, haven't experienced any crashes at all, other than when I enabled collision support.

Mind you I haven't had anymore than 5 people on at a time...
 
MMm.. no daedelus82,

i think that the version is not stable.... Maybe we should be wait for next updates....
What stable version do you have?... Could you tell me some version better than 3.5?

Some version without crashes.... please..jeje...


Actually it was my f**k up.. The vmaps I was using I made with an older version of vmap_extract/assembler.
I compiled vmap_extract and assembler and made a fresh set of vmaps... Works perfectly! :)

Here is a screenshot of a level 23 character I made in stockade, you can see how the mobs inside the room haven't aggro'd.. Works perfectly!



If you want a copy of my compiled Ascent 3936 stable, with the heal-over-time fix applied, and vmaps enabled let me know...
 
Thanks!!

I will test this evening... How can i get the last update of vmaps and collision.dll?
and, one time get it, how can i activate in my ascent-world.conf?
 
You don't edit anything in ascent-world.conf...
To get collision support you have to compile it with collision support.
See the ascentemu wiki
 
Daedelus82,

i can't compile it because i haven't visual 2008... I always download the ascent version and install the ncdb only...
Normally the vmaps and collision is inside the ascent.rar,

Then, if this files are with rar file, what can i do?.. Only left the collision.dll in the folder root with ascent.exe?...
 
I'll compile one for you

EDIT: 3.8 stable revision 3963 with collision support


All you need to do is edit the conf files, and extract/copy dbc, maps, and vmaps for 2.3.3.

Check the ascent wiki if you are unsure how to do any of this.

 
hi daedelus82,

Thank you very much for your compiled 3963 version!! I have installed it and works fine!!
But i can't go into stockade because the prisioners cross the walls... Perhaps i did something bad... i tell you:

I had the 1108 ncdb installed

1. I download your 3963 version
2. i executed the two files about vmaps in tool folder... and the process was long (about 30 minutes)
3. Then i changed the ascent-world.conf, ascent-logonserver.conf and ascent-realms.conf.
4. then i executed the 3 files in this order: first the ascent-world.exe, ascent-logonserver.exe and ascent-realms.exe

The ascent-realms.exe file throw an error message:

Connecting to mysql on localhost with (moccow: ********)
Access denied for user moccow '@' localhost
one or more errors occured while connecting to databases

i know that my user of mysql is other.. but i don't know where i must to chage it... I have been finding this moccow user in the 3 conf files but nothing... i couldn't see it...

Is useful this ascent-realms.conf? i can play with ascent-world.exe and logonserver.exe... Maybe yoy know what happend to me with this file and if is necesary to fixed it...

And the collision.dll doesn't work to me... I executed the vmap_assembler.exe and vmapextract_v2.exe and now i have a folder (called buildings) with 4425 wmo files..
they must be in this path?

what can i be doing bad?

thaks for your help
 
All you need to avoid this error is to dl+install the Microsoft Visual C++ 2008 Redistributable Package (x86) , not the entire .NET framework crap.

Here -->
 
Back