Login and Launcher Issues: September 2nd, 2013 Last Updated 1:42 PM Eastern

[jessy101]

Launcher hanging at "Installing Pre_Reqs"

any ideas on why this is happening?

[jessy101]

any ideas on why this is happening?

anyone running into this problem try running as an admin and see if that works

[PNellesen]

anyone running into this problem try running as an admin and see if that works

EDIT: Just logged out, then tried without running as Admin, and I'm able to get in again. May be a one-time thing?

This worked for me.

But this begs the question, what did they do now? Didn't have to do this last night.

Find it hard to believe it's not related, but I did a pre-install of the Lammania client this morning, and this "Installing Pre-Reqs" issue started immediately afterwards.

[jessy101]

Launcher hanging at "Installing Pre_Reqs"

look on last page this may and or may not work but give it a shot

[Vivanto]

Launcher hanging at "Installing Pre_Reqs"

I'm joining the club. Just finished a raid without being able to loot every chest, of course.

[jessy101]

This worked for me.

But this begs the question, what did they do now? Didn't have to do this last night.

Find it hard to believe it's not related, but I did a pre-install of the Lammania client this morning, and this "Installing Pre-Reqs" issue started immediately afterwards.

i agree and wonder what will it take for them to get this right the first time around ye kno. i can tell you i never downloaded the lam. sever and ran into this problem

[Draeqo]

This worked for me.

But this begs the question, what did they do now? Didn't have to do this last night.

Find it hard to believe it's not related, but I did a pre-install of the Lammania client this morning, and this "Installing Pre-Reqs" issue started immediately afterwards.

That should not make any difference, but then my work around is also a bit odd.
It seems a kind of self-locking issue with how the client starts.
Starting as admin will not (or should not) prevent that.
What does seem to work is if the client is simply started 'differently', for just this one time.
One easy option is to kill (not close the normal way) the hanging client and directly start a new client.

How To:
Go to task manager and look on the second tab 'Processes'.
Select TurbineLauncher.exe and End Process (via button or via right-mouse click)
Start DDO again.

Works for me

[Vivanto]

That should not make any difference, but then my work around is also a bit odd.
It seems a kind of self-locking issue with how the client starts.
Starting as admin will not (or should not) prevent that.
What does seem to work is if the client is simply started 'differently', for just this one time.
One easy option is to kill (not close the normal way) the hanging client and directly start a new client.

How To:
Go to task manager and look on the second tab 'Processes'.
Select TurbineLauncher.exe and End Process (via button or via right-mouse click)
Start DDO again.

Works for me

I think it's more mystical than that, some sort of DDO dark magic. Cause I've done that several times, router restart, pc restart, everything.

However, after reading your comment I just decided to try the task manager method one more time, and it seems to have worked. So in conclusion, any workaround will only work if someone already tried, succeded with it and posted it on the forums, but not before (yeah, there's a big fallacy here, but nvm).

[die]

That should not make any difference, but then my work around is also a bit odd.
It seems a kind of self-locking issue with how the client starts.
Starting as admin will not (or should not) prevent that.
What does seem to work is if the client is simply started 'differently', for just this one time.
One easy option is to kill (not close the normal way) the hanging client and directly start a new client.

How To:
Go to task manager and look on the second tab 'Processes'.
Select TurbineLauncher.exe and End Process (via button or via right-mouse click)
Start DDO again.

Works for me

Nice that just worked for me also , but why the problem I wonder if it has too do with them putting up lammania today

[Draeqo]

Nice that just worked for me also , but why the problem I wonder if it has too do with them putting up lammania today

Ah, if that is what they are doing it may be caused by (erroneous) internal redirection on DDO's side.
Nothing that we can combat on our side, apart from retrying & hoping that the next time we are redirected correctly, LOL.

Anyways, another variant that seems to work is to simply not kill or close the first hanging client, but first start-up a second one, see it progress correctly and only then close the first hanging client (if you try to kill the old one, you may end-up killing the good one ...).
Had to relog just now & had the issue again, so tried this succesfully .

Note that if this is a client session redirection error, the wrong rerouting algo may keep you in the wrong redirection because connections (from same IP & client) can be made 'sticky'.
So if you close your client and try again you may end-up with the same (wrong) connection session.
Which is why retrying it several times (and closing the program every time first) may very well not work.
By starting up a second client you should get another connection & that one may (finally) work ...

[Lutehor]

Tried everything cant get in. Anyone else notice this thread was started in Sept.

[DC_Nightfire]

I have windows 7 64x and was having this problem.
I opened a cmd window as admin then typed "ipconfig /flushdns"
restarted ddo and it worked fine.

hope that helps some people.

[Draeqo]

I have windows 7 64x and was having this problem.
I opened a cmd window as admin then typed "ipconfig /flushdns"
restarted ddo and it worked fine.

hope that helps some people.

Good one.
Yes that should also work if the issue is hanging sessions / misdirected network sessions, as that will also ensure that you get a new connection session

[Zavier]

Launcher hanging at "Installing Pre_Reqs"

This has been happening for at least 3 or 4 days for me. Launcher hangs. I close launcher. Launcher hangs. I close launcher. Eventually launcher proceeds normally. I am glad to see this is more widespread than myself

[Brunhildha]

EDIT: Just logged out, then tried without running as Admin, and I'm able to get in again. May be a one-time thing?

This worked for me.

But this begs the question, what did they do now? Didn't have to do this last night.

Find it hard to believe it's not related, but I did a pre-install of the Lammania client this morning, and this "Installing Pre-Reqs" issue started immediately afterwards.

For me, I had to run one PARTICULAR launcher as Admin. They give you lots of choice

They are dndlauncher.exe., Turbinelauncher.exe and Turbineinvoker.exe all in your DDO programme folder. (Not the DDO docs folder).
Normally each one calls up the next. Its something to do with patching updates properly and there is a thread somewhere that explains it. It seems unnecessarily complicated to me, and I never understood it.

Anyway the icon in your start menu calls up dndlauncher.exe but running that as admin did not work for me. I had to run Turbinelauncher.exe as Admin to get over this problem. Once run successfully, it reverted back to normal, and I can use the normal icon in the start menu.

Patch on repair on darning on old knitting, eh?

[PSU_Lion]

I keep getting Connection failed client time out the connection. *** Please help!!!!!

[Draeqo]

I keep getting Connection failed client time out the connection. *** Please help!!!!!

Hi, please see some options in the thread above.

Basically what probably is happening is that it is related to network sessions, most likely on DDO side, that are not going anywhere.
It may be the result of 1 or a few networkadresses on DDO side pointing to thin air (i.e. nothing) after they did some internal network rerouting.
Just imagine that you normally connect to one of many connectionpoints, which one of them is random; but now some of them are broken.

So the easiest solution would seem to be to simply stop the client & retry.
However it is normal for such sessions from your PC to the DDO servers to become sticky.
As a result you will get the exact same session back when you close the client and try again by starting up the client again.

Some options that will help to prevent you getting the same (broken) session are:
- ipconfig /flushdns, as described above
- start up a second client with the old one is still running, after second one starts succesfull you can close old one

What also may work are:
- start up a client as admin (assumes that the current one isn't by the way)
- kill not close client (via taskmanager) and start-up new (quickly IMHO)

The first options are best to try.
Note that you may still get a broken connection on your 2nd attempt (you rolled a 1 again ), just retry using one of the options above and it should work on 2nd or 3rd attempt.

[SirCrazyRob]

i cant get in game! tried flushing dns, tried running as admin, (all 3 launchers) tried closing via task manager, tried having one window open then starting another!! wtheck is goin on???

[SirCrazyRob]

i cant get in game! tried flushing dns, tried running as admin, (all 3 launchers) tried closing via task manager, tried having one window open then starting another!! wtheck is goin on???

and when the launcher DOES come up, i get a "an update error occurred, server connection timed out" then it waits for 60 sec and does it again. When i do (rarely) get to a log on screen, it cycles through "connection attempt 1-20" then kills itself after 20!

[Mindos]

and when the launcher DOES come up, i get a "an update error occurred, server connection timed out" then it waits for 60 sec and does it again. When i do (rarely) get to a log on screen, it cycles through "connection attempt 1-20" then kills itself after 20!

Are you running windows firewall? You may want to check the program list. I find it easier to remove the program, then let the notice popup to accept.