First I copied the folder from our dev server to our production server.  Then I used that installation steps on this site to ensure that IIS was setup properly.  I tried hitting the website and I get webconfig errors because our database was SQL. 

 So I Moved the SQL database from our dev environment and attached it to our production environment and changed the webconfig accordingly.  But now instead of an Error Message or the website displaying I get this.

	Internet Explorer cannot display the webpage
	Most likely causes: You are not connected to the Internet. The website is encountering problems. There might be a typing error in the address.
	What you can try:
	Diagnose Connection Problems
	More information This problem can be caused by a variety of issues, including: Internet connectivity has been lost. The website is temporarily unavailable. The Domain Name Server (DNS) is not reachable. The Domain Name Server (DNS) does not have a listing for the website's domain. If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.   For offline users You can still view subscribed feeds and some recently viewed webpages. To view subscribed feeds Click the Favorites Center button , click Feeds, and then click the feed you want to view.   To view recently visited webpages (might not work on all pages) Click Tools , and then click Work Offline. Click the Favorites Center button , click History, and then click the page you want to view.

----------------------------------------------------------------------------------

 There is nothing on your website about DNS settings.  I can hit the website just fine but not the Graffiti site within it.  Any thougths, ideas or any help would be greately appreciated.

 Regards,

RAFF

Make sure default.aspx is your default document in IIS - sounds like it's not hitting the page.

 (do you have an external link?)

Jayme

I'll try that!  Thank you. 

Here is the link goes it's http://www.accessrx.com/health-articles/default.aspx

it is actually setup as the default document.  It goes in this order

1. Default.aspx
2. Default.asp
3. Default.htm
4. index.htm

If you go to the asp.net tab, is asp.net 2.0 selected?

Jayme

In the asp.net tab I have

Asp.Net version: 2.0.50727 selected
Virtual path: /health-articles
File Location: PATH\accessrx.com\health-articles\web.config
Creation Date: 7/9/2008
Last Modified: 7/9/2008

Does this file exist locally on the server you are trying to reach? Does the root directory work? Perhaps you need to regen site files in the control panel utilities section?

Jayme

The files are on the server and I can show you this if I break the webconfig I actually get asp.net error page.  The thing is that the main site is a classic asp site and we have embedded graffiti in a folder within the site.  It's working on our dev environment, but there is nothing I can do so far to make it work on the production server.

As far as doing a regen using the control panel utilities section.  Is this assuming I can login to the graffiti-admin directory?  Because if it is sadly I can't load that up.

 Thank you for helping me so far I really appreciate it.

If I hit this link it works

 http://www.accessrx.com/health-articles/error.htm

 But is not .net just html page, but at least it shows it's up.

Interesting I got it to work by removing the following code

 /*

        bool isWWW = wwwStatusRegex.IsMatch(Request.Url.ToString());
        string redirectLocation = "http://www.accessrx.com";
        if(isWWW && !SiteSettings.RequireWWW)
        {
            redirectLocation = wwwStatusRegex.Replace(Request.Url.ToString(), string.Format("{0}://", Request.Url.Scheme));
        }
        else if(!isWWW && SiteSettings.RequireWWW)
        {
            redirectLocation = noWwwStatusRegex.Replace(Request.Url.ToString(), string.Format("{0}://www.", Request.Url.Scheme));
         
        }
       
        if(redirectLocation != null)
        {
            if (redirectLocation.ToLower().EndsWith("default.aspx"))
                redirectLocation = redirectLocation.Substring(0, redirectLocation.Length - 12);
           
            Response.RedirectLocation = redirectLocation;
            Response.StatusCode = 301;
            Response.End();
        }
 */

 from the Global.asax file

I'm having exactly the sme problem as you describe, but had to comment everything out in the global.asax file. Naturally, the rest of the site doesn't work after that, but at least i get to the login page.

I've checked the event viewer logs and this is what I can see:

"Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module kernel32.dll, version 5.2.3790.4062, stamp 46264680, debug? 0, fault address 0x0000bee7.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

Anyone knoew what top make of this?

By the way, we are running the express edition (to test it) on a windows 2003 server with MSSQL 2005. Also, the site runs on its own app pool.

Hi,

just got the same DNS error. The funny part ist that I already successfully run a Graffiti website on my hosted webspace (1und1 Germany).

Running fine for quite some time now:
Graffiti 1.0.1 with MSSQL in a subfolder of main ASP site; tweaked.

Just installed as a demo for someone else:
Graffiti 1.1 (latest "refresh", just downloaded today) with VDB3 in another subfolder of main ASP site; default theme and config. Expected it to be a point'n'click no-brainer install and now I'm loosing time (and patience) ...

Both subfolders marked as Applications. Tried commenting out the redirectLocation Part in Global.asax without success. File error.html shows up. Config with customErrors off shows .NET errors as expected.

May the problem be the 2nd install on the same machine?

Jim

Ceterum censeo: I'm getting disapointed regarding the lack of telligent action on this software ... v2 = Q1/2009 ... blog June 20, 2008 ...

Follow-up: I just deleted all those v1.1 files out of my intended demo website and installed an unmodified v1.0.1 instead (only changed RequireWWW=true and customErrors=Off). That started up and worked without any problem. So the app folder works well ...

Conclusio: As my own Blog that I started with v1beta1 only got updated upto v1.0.1 for now, and I was not able to get that demo website running under v1.1 now I must presume that v1.1 does not run in my production environment. I wonder if that release may have some issue due to that shared hosting under medium trust?

 Is there anywhere I can download 1.0.1 instead 1.1 to test if it works better?

Next follow up: 

JimS:

I was not able to get that demo website running under v1.1 now I must presume that v1.1 does not run in my production environment

Mmh, out of curiosity I created a third subfolder to my domain and tried v1.1 again – and it just worked. I can't find any obvious reason why the first attempt with v1.1 didn't.