02-08-2010, 10:37 PM
Hi again,
First off, excuse me for my bad English.
I wrote another thread earlier about running Urlblast on windows 7. That was resolved by updating to 1.7 and works great on my development enviroment.
I have ported the Web UI to Silverstripe, a CMS which makes it easier to build and improve the frontend, and i'm in the phase of deploying it live.
However, the live server is a Windows 2008 machine, and i just can't get it to work. The Urlblast does not start, it just creates a new window which stops to respond(crashes) before the main window is shown. That is, it is in the taskbar and having the window title as the computer name. It can't be closed properly but needs to be forced to close.
I came past the defrag phase though.
I'm using the exact same configuration as on the Windows 7 machine. Every directory is the same.
Does anyone have a clue on what this could be or are there any issues running on a windows 2008 server?
/Patrik
Edit: Also tried to update with the 219 build with a similar result. The application crashes but now the main window is visible.
First off, excuse me for my bad English.
I wrote another thread earlier about running Urlblast on windows 7. That was resolved by updating to 1.7 and works great on my development enviroment.
I have ported the Web UI to Silverstripe, a CMS which makes it easier to build and improve the frontend, and i'm in the phase of deploying it live.
However, the live server is a Windows 2008 machine, and i just can't get it to work. The Urlblast does not start, it just creates a new window which stops to respond(crashes) before the main window is shown. That is, it is in the taskbar and having the window title as the computer name. It can't be closed properly but needs to be forced to close.
I came past the defrag phase though.
I'm using the exact same configuration as on the Windows 7 machine. Every directory is the same.
Does anyone have a clue on what this could be or are there any issues running on a windows 2008 server?
/Patrik
Edit: Also tried to update with the 219 build with a similar result. The application crashes but now the main window is visible.