Rdwebapp Problem..!

iphonogasm

Well-known member
Joined
Jun 19, 2011
Messages
247
Location
New Zealand
Hi,im trying to deploy the Site in IIS for RDWebApp for application sharing.

When adding the website in IIS, i am receiving the following errors. I am using the correct binding etc and all Application Pools exist etc.

Thanks!

Server Error in '/' Application.

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /RDWeb/Pages/default.aspx/
 
Check your URL:

/RDWeb/Pages/default.aspx/

It cannot be right, the last SLASH shouldn't be there, it should look like this:

/RDWeb/Pages/default.aspx
 
Thanks but im getting the same error without the "/"

Thanks!

Server Error in '/' Application.

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /RDWeb/Pages/default.aspx
 
Check in your settings of IIS where is the folder for your content (C.\IIS\) and if there are all the subfolders, in your you must have: \RDWeb\Pages\

If you don't know, search with windows search.
 
Your root app (/) is pointing where? If you manually navigate into /RDWeb/Pages/ and you open the file default.aspx, does it work?
 
what the... you should be able to open it... well at least we know it exist and contains something.

Anyway, where is pointing the main app (root app)?
 
What u mean, i cannot see where application pool is pointing for some reason?

Its like it cant find the resources!

Thanks! this is annoying im despirate!

heres the code of default.aspx











void goToFolder(string getLangVal)
{
Response.Redirect(getLangVal + "/Default.aspx" + Request.Url.Query,true);
}

void Page_Load(Object sender, EventArgs e)
{
string langCode = null;
System.Globalization.CultureInfo culture;

// For each request initialize the culture values with
// the user language as specified by the browser.
if (Request.UserLanguages != null)
{
for (int i = 0; i < Request.UserLanguages.Length; i++)
{
string strLanguage = Request.UserLanguages;

// Note that the languages other than the first are in
// the format of
// ";" (e.g., "en-us;q=0.5")
if (strLanguage.IndexOf(';') >= 0)
{
strLanguage = strLanguage.Substring(0, strLanguage.IndexOf(';'));
}

try
{
culture = System.Globalization.CultureInfo.CreateSpecificCulture(strLanguage);

// Make sure that the directory is present
string physicalPath = Server.MapPath(culture.Name + "/" + "default.aspx");

if ((physicalPath.Length != 0) && (System.IO.File.Exists(physicalPath)))
{
langCode = culture.Name;

break;
}
}
catch (Exception)
{
// Some cultures are not supported and will cause an
// exception to throw. In this case,
// we ignore the exception and try the next culture
// based on client language preference.
// Note that if no culture can be set properly, then
// the default culture will be used.
}
}
}

if (String.IsNullOrEmpty(langCode))
{
// Default to Installed language
culture = System.Globalization.CultureInfo.InstalledUICulture;

// But first make sure that the directory is present
string physicalPath = Server.MapPath(culture.Name + "/" + "default.aspx");

if ((physicalPath.Length != 0) && (System.IO.File.Exists(physicalPath)))
{
langCode = culture.Name;
}
else
{
try
{
// In some cases we have to use common culture parents to determine where to redirect
// We gather up the hierarchies of the ui culture and of installed language cultures
// comparing their hierarchies until we find some sort of match
physicalPath = Server.MapPath(".");
System.IO.DirectoryInfo dirInfo = new System.IO.DirectoryInfo(physicalPath);
System.IO.DirectoryInfo[] cultureDirectories = dirInfo.GetDirectories("*-*");
langCode = "";

while(culture != culture.Parent && culture.Parent != null)
{
culture = culture.Parent;

foreach(System.IO.DirectoryInfo cultureDir in cultureDirectories)

{
System.Globalization.CultureInfo ci = System.Globalization.CultureInfo.CreateSpecificCulture(cultureDir.Name);

while(ci != ci.Parent && ci.Parent != null)
{
ci = ci.Parent;

if(ci.Name == culture.Name)
{
langCode = cultureDir.Name;
break;
}
}
}

if(langCode != "")
break;
}

}
catch(Exception)
{
// See above about cultures and exceptions, in this case we fallback to en-us
}
}

// fallback to english if all else fails
physicalPath = Server.MapPath(langCode + "/" + "default.aspx");
if ((physicalPath.Length == 0) || !(System.IO.File.Exists(physicalPath)))
{
langCode = "en-us";
}
}

goToFolder(langCode);
return;
}



In application settings in IIS

i have

RDWebAccessConfigPath

and

DefaultCentralPublishingPort

Thanks!
 
When you open IIS manager on your left you have all the app pools and so on. Well, somewhere you should have the primary, the root ( / ). Right click on it and select properties. I'm quite sure that your app is pointing to the wrong app pool.
 
When you open IIS manager on your left you have all the app pools and so on. Well, somewhere you should have the primary, the root ( / ). Right click on it and select properties. I'm quite sure that your app is pointing to the wrong app pool.

There appear to be no application assigned!
 
damn right now I can't remember... but there's an option (somewhere in settings) where to point exactly. If you find it, point (again) to the folder "RDWeb\Pages\"
 
i got it working. Removed the RD web access role, deleted all websites related to it restarted, reinstalled the role and still was no website.

Confused, so i created a new site.

Firstly, it doesnt create a "new" site, it add the directorys as "Applications" to the existing Default Site. Which leads me to a quick off topic question, what determines a site to be the "Default Site" ? In this case it was my MegaHosting site and had created the Applications/VirtualDirectoys RPC, RDWeb etc.

Before i knew all this, i was creating the website RDWebApp, and pointing it to C:/Windows. Thus leading to issues because the folder name in Web is actually "RDWeb"

Renamed the website to RDWeb (probably more the path), converted the RDWeb Directory to an application all is go. A bit confusing....

But yea,any ideas what determines a website to be the Default Website, and anyway to change this??

Thanks for all your help as usual !! :)
 
I have no idea... this looks like a service (IIS) stucked somewhere...

Default Web Site is the pre-configured website which shows you the IIS logo and stop. Usually you remove the default web site to create your own.
 
Back
Top