I'm currently work on a 7.0.4-based website. Until yesterday this was done on my own pc (localhost).
Then I copied the site onto our development IIS and thus pointing towards the same SQL db as before.
Everyting seems to work fine - both visitors UI and backoffice UI.
However, my collegues accessing the newly copied site can see the public/visitors pages but - when following the url I provide site admins - the black welcoming login page does not show. Only a copmpletely white page is displayed to them - not the login form.
But the DB is the same (also MSSQL) as when the site was on my local machine. During install on my local machine I set up a connection string to our MSSQL server - which is the same as the one used by the "new" site (in orther words: same web.config pointing to MSSQL db).
Ehm...so your colleagues are trying to access the solution on their local machines? Are they accessing it from their localhost or are they connection to your machine? Or are they developers like you and need to work on the code etc.?
I'm a bit confused that they can access and see the frontend but can't access the backend...
I think we have nailed the problem. The issue seems to be IE9's inability to interpret hash-char in the url genereted via til hostname/umbraco - in our case:
Login page blank - 7.0.4
Hi,
I'm currently work on a 7.0.4-based website. Until yesterday this was done on my own pc (localhost).
Then I copied the site onto our development IIS and thus pointing towards the same SQL db as before.
Everyting seems to work fine - both visitors UI and backoffice UI.
However, my collegues accessing the newly copied site can see the public/visitors pages but - when following the url I provide site admins - the black welcoming login page does not show. Only a copmpletely white page is displayed to them - not the login form.
We've tried:
http://umbraco.deviis2.bshus.bsh/umbraco
http://umbraco.deviis2.bshus.bsh/umbraco/umbraco
http://umbraco.deviis2.bshus.bsh/umbraco/login
http://umbraco.deviis2.bshus.bsh/umbraco/login.aspx
and
http://umbraco.deviis2.bshus.bsh/umbraco#/login?check=false
With no luck :-/
Hi Folke
Could you by any chance migrate the CE SQL database to MSSQL instead? CE SQL can have some weird issues where content is not saved etc.
/Jan
Hi Jan
Tanks for your reply
But the DB is the same (also MSSQL) as when the site was on my local machine. During install on my local machine I set up a connection string to our MSSQL server - which is the same as the one used by the "new" site (in orther words: same web.config pointing to MSSQL db).
Best Regards
Folke
Hi Folke
Aaah, sorry misread your initial post :)
Ehm...so your colleagues are trying to access the solution on their local machines? Are they accessing it from their localhost or are they connection to your machine? Or are they developers like you and need to work on the code etc.?
I'm a bit confused that they can access and see the frontend but can't access the backend...
Looking forward to hearing from you again.
/Jan
Hi Jan
Thanks for your help!
I think we have nailed the problem. The issue seems to be IE9's inability to interpret hash-char in the url genereted via til hostname/umbraco - in our case:
http://umbraco.deviis2.bshus.bsh/umbraco#/login?check=false
What happens is that IE9 (our intance at least) strips out the #-char and any chars following it - leaving us with:
http://umbraco.deviis2.bshus.bsh/umbraco and an entirely white page.
Not quite sure how to handle - but at least I think we know the cause now.
Kind regards
Folke
Hi Folke
Aaah yes that could perhaps be an issue. You could try filing it as a bug on http://issues.umbraco.org/issues
Cheers, Jan
Hi Jan,
Thanks
I think I'll post it when I'm comppletely certian that this is in fact the cause of the problem ;-)
Have a nice day and weekend :-)
Regards
Folke
Hi Folke
Good idea - And thanks! Same to you :)
/Jan
If you still have this problem and the solutions in this thread hasn't solved it for you, please look at my post here:
https://our.umbraco.org/forum/getting-started/installing-umbraco/54708-A-server-error-occurred-=-completely-stuck
is working on a reply...