Using Umbraco with Subfolders - iis

I have built an Umbraco project (7.2.2) on my local machine and it all works well. I now want to copy it to our test server running IIS 7.5.
I have created a Virtual Folder in IIS under the default web site and copied the project across. The url I am using is www.ourserver.com/testumbraco. I can access the content ok but if I try to login to edit the content I get a blank page (umbraco#/login/false) and shortly afterwards it returns to the login page with Session timed out.
If I Inspect the page I can see that some resources have failed to load with Error 404. It is looking for www.ourserver.com/umbraco and not www.ourserver.com/testumbraco/umbraco.
Is there a configuration setting I need to change to make this work properly?
Thanks in advance for any suggestions.

You need to update the umbracoPath setting in the web.config

Related

Fix razor WebPages with friendly URL returning 404 error

I have a website written as razor ASP.Net code wit the extension .cshtml. I wrote the site using WebMatrix and the site runs fine when i run it on web martix's "LocalHost". The links and all my code work, but as soon as I try to run the website from my IIS server the page links no longer work properly. When I click on a link it returns the 404 error page. If I type in the .cshtml extension the page loads correctly and all is right with the world except the file extension. The only page that still works is the index page because it is a default page.
Every place I've checked says that it should run without the extension as a default of asp.net or if it doesn't run as default then use the url re-write plugin.
The Default isn't running and I am unable to use the URL rewrite tool.
What can I do to get the default to work or is there another way to have the extensions not display without using URL re-write
ps. I know that if I put the files in a folder with the link name and rename them to index.cshtml This will work but I feel it is a very backhanded way of doing it so I would prefer not to do it that way.
pps. before any one suggests a solution for mvc I am explicitly NOT USING MVC Logic. thank you.
Try two things:
Set the application pool to ASP.NET 4.0. Then restart I IIS.
Add the following key to <system.webServer> section of Web.Config:
<modules runAllManagedModulesForAllRequests="true" />

Error in non existent global.asa

I have a user's website giving an error in a global.asa file but it does not exist in their web root. It looks like the account has been hacked as it's giving an error about not connecting to a server, and at the same time I see the firewall block outbound connection requests.
msxml3.dll error '80072efd'
A connection with the server could not be established
/LM/W3SVC/6510/ROOT/global.asa, line 66
I've deleted the IIS instance and had the control panel recreate it, but the issue still exists. I've even created a dummy asp file which only displays some text and it happens.
I'm at a loss where this could be being picked up and looking for suggestions. Where might this be set?
I've had the same problem on a w2k3 server (iis6) with many sites, where just one had the fake global.asa;
I've not still found cause but a workaround solution, for me, has been:
open MMC Console (IIS manager)
stop IIS
double click on Web Sites (confirm reload offline configuration)
under every site delete "ghost" global.asa (that you don't find under phisical websites folder)
start IIS

Modx Unable to login to manager area

I've just transferred a modx site for a client over to fasthosts - got the site setup working fine but when logging into the backend I'm getting Incorrect Username / Password.
I know that the credentials are correct.
Any ideas?
Using 1.0.4
I've heard of similar issues before when people migrate a site to a shared host. Does this solution help?
I've fixed it!
It seems to create all site content including paths and sessions within files on server... So obviously I'd ftp from old host to new host, put live expected to work which front end did because it doesn't use session data but then the backend had it's knickers in a twist
I setup a new installation with a db prefix test_ - once site was installed changed db parameters then cleared site cache, uploaded new template files etc.
Cheers
Shane

Asp.Net publish on server does not some html controls

I have a web application which works fine when i publish and host it on my localhost ...
The same published folder i host to a remote server and a few controls go missing on load of the page .I log into remote desktop to the server and try opening the site on the server itself it works fine. But only when i access it from my local system some controls go missing .Is there something i am missing on the Browserused on the swerver as well as my local system is IE 8 .
Thanks & Regards,
Francis P.
You probably have some URLs with a hard-coded http://localhost/....
Change all of your absolute URLs to relative URLs.
Fiddler and Firebug will be very helpful to see which URLs are being requested.

Uable to access sharepoint site

I turned on directory browsing (in IIS) for my sharepoint site, then turned it off again and now every time I try to access the site through a web browser I get 404 error, page cannot be found.
I know it's something to do with authentication but don't know where to start looking/fixing ?
Can you give a bit more background? Do you get 404's for all pages? Can you hit layouts pages? E.G:
http://YOURSITE/_layouts/settings.aspx
404's in SharePoint shouldn't be taken at face value. Check your ULS logs in:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS
We ran into a smiliar issue yesterday
More of a work around this:
Rather than try to figure out what permissions to set/reset, just delete the web application, specifying Yes to 'Delete IIS Web' sites and No to 'Delete content databases'.
This will keep the content database (with all your content you can't currently access).
Then create a new web application with the same name and host header and enter the existing content database name.
This should then recreate the IIS web app with correct permissions and connect to the existing content database.

Resources