xgecko - Friday, January 6, 2012 12:11 PM:
I ditched the SBS 2008 OS and redid my server with 2008 R2. Install of Innovator went smoothly however when I try to connect via browser I get a blank explorer window. I have not found any workable solutions. We need to get this working so we can evaluate it and have made little to no progress to date.
Can anyone point me to a solution to this problem?
galderson - Friday, January 6, 2012 1:16 PM:
Hello xgecko,
I have also just installed Aras recently and I experienced a similar problem noted the following post: www.aras.comhttp:/.../2138.aspx
I would review the client configuration steps for IE and run the .NET configuration tool after applying IE settings changes. A second time through did the trick for me with IE 9.
xgecko - Friday, January 6, 2012 1:32 PM:
Hi,
Thanks for the suggestion but I have done all that already to no avail.
xgecko - Friday, January 6, 2012 3:00 PM:
More info: I got further when trying to start Innovator on the server; it appears I need to install XML 4.0 and it might work there. Currently installing a bunch of other updates that showed up once I added MS update to the updater. Will report back as I gather more data.
xgecko - Friday, January 6, 2012 5:13 PM:
Even more info... and some good news! I rebooted after installing msxml on my client and managed to get into the system as admin! We shall see if this persists. For now, at least until Monday, it looks like I am ready to move forward finally. Assuming I can get in again on Monday we should be able to begin our evaulation.
Thanks!
Anonymous - Friday, January 6, 2012 5:34 PM:
Hi xgecko,
I was reading your post and about to state to make sure that you had IE running in compatibility mode and be sure to have .Net 3.5 on the client side. You may still want to double check these items. Congratulations on getting connected as an admin.
eva
xgecko - Friday, January 6, 2012 5:42 PM:
I had been all through the checklist several times. The one thing that may or may not have done the trick was the installation of msxml on the client, or maybe just rebooting after failing so many times. Will have to see how it goes on Monday, but initial results are very promising.
Thanks!
