Tuesday, December 20, 2005
« 2nd Utah Geek Dinner | Main | Additional House Projects »

I was working with a customer today on an issue.  The customer had a custom VS project that he had inherited from another developer who had since left the company on other pursuits.  While the original developer could work in the solution just fine, the new developer was receiving the following error message:

Visual Studio .NET cannot create or open the application.  The likeliest problem is that required components are not installed on the local web server.  Run Visual Studio .NET setup and add the web development component.

Naturally the first thing I tried was to repair IIS with the following commandlines:

cd %windir%\Microsoft.NET\Framework\v1.1.4322
aspnet_regiis -i

That didn't fix the error, though I didn't really expect it to - the .NET extensions were all already properly mapped in IIS.  The solution was (unlike all of the recommendations that I found online to run the aspnet_regiis utility) to fallback to the same solution that had solved another issue a long time ago:  to delete the VSWebCache folder.

The VSWebCache folder is created automatically by Visual Studio when you open/create a web project and can be found in <root>\Documents and Settings\<user>\VSWebCache\<machinename>.  Simply delete this folder and VS will recreate it when you attempt (now successfully) to open the web project.

Tuesday, December 20, 2005 4:06:00 AM (Mountain Standard Time, UTC-07:00)  #    Disclaimer  |  Comments [89]  |  Trackback
Monday, January 09, 2006 4:23:00 AM (Mountain Standard Time, UTC-07:00)
Thanks for this post. We were having problems with our Final Builder script when compiling our project during the build. It kept failing on the web project in our solution and once we added a manual step to delete the VSWebCache, it fixed our problem.
Mike Finley
Saturday, January 21, 2006 7:01:00 PM (Mountain Standard Time, UTC-07:00)
i still have the problem, i think that return that assign default hosting to my iis, when i remove it. its working okay, but i need to keep it so the cusomer could connect from out the company, anyone have idea what can i do?

Matoo
Sunday, January 29, 2006 8:43:00 AM (Mountain Standard Time, UTC-07:00)
awesome!! this fixed my problem straight away.
lomaxx
Monday, February 06, 2006 12:01:00 PM (Mountain Standard Time, UTC-07:00)
Thank you!!!!
Annette
Wednesday, February 15, 2006 8:04:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Good tip.
anonymous rating
Wednesday, February 15, 2006 8:04:00 AM (Mountain Standard Time, UTC-07:00)
great suggestion. Thanks.
Amrita Marino
Friday, March 03, 2006 7:13:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
thanks a lot
bins
Sunday, March 19, 2006 7:13:00 PM (Mountain Standard Time, UTC-07:00)
not ay all working...!!!
sudipto
Sunday, March 19, 2006 7:15:00 PM (Mountain Standard Time, UTC-07:00)
i have tried all combinations to solve this but still i m getting the sam error...!!!!
sudipto
Monday, March 20, 2006 3:04:00 AM (Mountain Standard Time, UTC-07:00)
So what have you tried, sudpto? I'm more than happy to look into it with you.
Tuesday, March 21, 2006 11:17:00 AM (Mountain Standard Time, UTC-07:00)
I have delete the VSWebCache folder but it does not resolve the problem for me.
Monday, April 03, 2006 5:02:00 AM (Mountain Standard Time, UTC-07:00)
I'm still getting the error myself. I've deleted the folder and played with wwwroot folder permissions. Still no luck. I can use some externally created web apps and some I can't.





g
GregEcy
Monday, April 03, 2006 5:07:00 AM (Mountain Standard Time, UTC-07:00)
GregEcy,



Are you getting this error using Visual Studio 2003? (I've not experienced it using VS 2005). You should be able to simply delete the VSWebCache folder and call it good; make sure VS isn't open when you do it. Also, you might try deleting the website from the %WINDIR%\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files folder. Make sure that you (or the site's impersonated user) has Full Control on the Temporary ASP.NET Files folder (you might also try granting permissions to the %WINDIR%\Temp folder. Hope that helps. If not, let me know and I'll work through it with you.
Monday, April 03, 2006 5:07:00 AM (Mountain Standard Time, UTC-07:00)
Try correcting the paths found in:



ProjectName.vbproj.webinfo

and

ProjectName.vbproj.vspscc



Hope this helps,

g
GregEcy
Wednesday, April 19, 2006 7:59:00 PM (Mountain Standard Time, UTC-07:00)
HI guys



If u got this error " "Visual Studio .NET cannot create or open the application. Web s ite 'http://localhost/Webapplication' not started on this Web server." then just do this:

Start->Run->inetmgr->Websites->Right Click on the Default Web Site-->Click Start.

Then open ur web appilcation...it will run as it used to.



regds

Amit
Amit Thakur
Thursday, April 27, 2006 8:48:00 PM (Mountain Standard Time, UTC-07:00)
Thank you so much. Solved my problem.
Pablo
Monday, May 22, 2006 6:16:00 AM (Mountain Standard Time, UTC-07:00)
Thanks a lot!
Vilanova
Monday, May 22, 2006 7:49:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Great !! It solved my problem.
Madhu
Sunday, May 28, 2006 5:59:00 PM (Mountain Standard Time, UTC-07:00)
What a cool solution. Thank you.
Deepak Magoo
Wednesday, May 31, 2006 5:51:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Very helpful THX
Curt Zarger
Sunday, June 11, 2006 1:45:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Great! Thanks Plenty
Varun
Sunday, June 25, 2006 8:15:00 PM (Mountain Standard Time, UTC-07:00)
Hi, if got this error:



"Visual Studio .NET cannot create or open the application. Web s ite 'http://localhost/Webapplication'...



when I open a project.



The projectt worked ok on the previous server (a windows 2000) but now it gives this problem on our new windows server. I can acces the web through 'http://newserver/webapplication' from my local machine, but I can't open it with visual.



The error is a little odd since I know there is no server on localhost, I'm trying to open the project on the server!



thanks for your help!
Jordi
Monday, June 26, 2006 10:11:00 AM (Mountain Standard Time, UTC-07:00)
Is the path correct in your .webinfo file? I'm assuming that you're using VS.NET 2003, correct? Are you attempting to open the project from web?
Tuesday, July 04, 2006 3:50:00 PM (Mountain Standard Time, UTC-07:00)
hi sudipto,

I got the same problem, but rectified by changing the webinfo file. this should work fine for u. Before modifying the path in webinfo do check for the write permission for that folder.

thanks,

Sushanth
Sushanth
Monday, July 10, 2006 10:49:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Awesome! Thanks!
Ben
Tuesday, July 11, 2006 9:50:00 PM (Mountain Standard Time, UTC-07:00)
??????? ? ??????? !
Marat
Wednesday, July 19, 2006 5:10:00 AM (Mountain Standard Time, UTC-07:00)
Deleding VSWebCache didn't help me but I fixed this error by creating a new site in IIS at the path of the path found projectname.vbproj.webinfo.



I had upgraded to a new computer, failed to re-create the site in IIS.
Dune
Thursday, July 20, 2006 1:10:00 AM (Mountain Standard Time, UTC-07:00)
After few month of research. This tip solve my problem
Pascal Girard
Monday, July 24, 2006 2:59:00 AM (Mountain Standard Time, UTC-07:00)
I'm having a similar problem and spent quite a bit of time looking into it, but not found a solution.

The problem is, currently I have a single website and when I create a new ASP.NET app in VS 2003, it works fine. If I then create a new website, completely unrated to the original, then the creation fails in VS 2003. If I then remove this site, it starts to work again. I am assuming its something to do with VS 2003 not knowing which website to use, but can't find anything relating to it
Jon Jones
Monday, July 24, 2006 10:49:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thank you!!!!!!!!!!! This really help me to solve the problem.
Sunday, July 30, 2006 3:43:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thanks a lot, my problem is fixed. I really appreciate it, cya n good luck!!
Thursday, August 17, 2006 9:46:00 PM (Mountain Standard Time, UTC-07:00)
Hi,

Since the error occured I have been able to create new projects close then re-open them but i get the error message everytime i try to open older projects.

My applications haven't been moved to a new machine, I have tried deleting the VSWebCashe folder and the paths in the paths .vbproj.webinfo files are correct and I have tried restarting IIS - nothing works.

Anyone have any idea what i should do?
Pepper
Friday, August 18, 2006 3:04:00 AM (Mountain Standard Time, UTC-07:00)
Pepper,



Have you tried deleting the respective folder out of the \Temporary ASP.NET Files folder? I would delete that + the VSWebCache folder, restart IIS, and try again through Visual Studio.



If that does not work still, is it possibly a permissions issue? Can you create other web projects? Does the project name match the folder and virtual directory name?
Sunday, August 20, 2006 10:14:00 PM (Mountain Standard Time, UTC-07:00)
I tried every solution suggested in these posts...but unfortunately nothing worked for me. I should also mention that I can open all the projects and can create new as well except just one. And I was able to do it well before.
Tuesday, August 22, 2006 10:34:00 AM (Mountain Standard Time, UTC-07:00)
I had this problem also and found the cause was that the bin folder of the web project had accidentally been added to source control. Deleting it from source control resolved the issue.
Janet McLean
Monday, September 04, 2006 1:27:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Great solution - my webserver crashed prventing me loading my projects and this fixed it. Perfect 5.
John Blair
Monday, September 04, 2006 8:29:00 PM (Mountain Standard Time, UTC-07:00)
Great post !!!
Jyotsna
Tuesday, September 05, 2006 2:21:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thanks
Daniel Bartholomew
Tuesday, September 12, 2006 2:33:00 AM (Mountain Standard Time, UTC-07:00)
Another possibility...



I was getting this error when attempting to open a project that had been copied from another developer's machine. I did a little digging on the ‘net and discovered that this is a common problem when moving an ASP.NET project from one developer’s machine to another. The “MSESalesApp.vbproj.webinfo” file (open it with an ascii editor - i.e. notepad) in the project folder stores the URL to the project – so it has to match the virtual directory name you have set up for it in IIS. This virtual directory is created automatically for you when you create a new project from scratch, but has to be done manually (as far as I know) when copying a project from one machine to another. I had already created a virtual directory for the project, but had named it something different than the original developer did - different from the name stored in the above file - so Visual Studio couldn’t find it. I deleted my original virtual directory and recreated it with the same name that the original developer had used (same name in the above file) and everything seems to be working now.



John Poe
Tuesday, September 12, 2006 2:36:00 AM (Mountain Standard Time, UTC-07:00)
Oops... in my post above, regarding the “MSESalesApp.vbproj.webinfo” file, replace "MSESalesApp" with the name of YOUR project. Doh!
John Poe
Saturday, September 16, 2006 5:59:00 PM (Mountain Standard Time, UTC-07:00)
sorry, dude that didnt work. nothing did actually. I am now deleting my VS and going back to open source, where I can actually create web apps winthing 5 sec. stupid microsoft.
Jenny
Saturday, September 16, 2006 5:59:00 PM (Mountain Standard Time, UTC-07:00)
Jenny, what did you try that didn't work?
Friday, September 22, 2006 1:52:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
I've been looking for this solution for 2 weeks. Thank you!
Glen
Friday, September 22, 2006 5:30:00 PM (Mountain Standard Time, UTC-07:00)
I've tried your solution with no effect. The problem in my situation is that VS2003 cannot create a new empty web project but it can open old ones. Also I can create from some other application web projects so I've checked that IIS and Framework are working ok.



Any other suggestion? Thanks in advance for your help



Vagelis
Vagelis
Monday, October 02, 2006 4:07:00 AM (Mountain Standard Time, UTC-07:00)
Thank you!

Big help!
Wednesday, October 04, 2006 4:01:00 AM (Mountain Standard Time, UTC-07:00)
I tried your solution to review the webinfo file and make sure it points to the right location after I copied code from other developer's machine. At first, it did not work. Then, I review the web application property in IIS and grant the Read privilege by checking the box. It works now.



Thank you,
jamesbin
Monday, October 09, 2006 6:16:00 PM (Mountain Standard Time, UTC-07:00)
Even i have tried the above mentioned solutions, buit nothing seems to work. But as i was trying out different things. I noticed one strange thing. In my Internet explorer, in the connection setting i was using a proxy server for my net access. If i disable my proxy server settting (remove the tick on the checkbox) then the application would load and run correcctly. I am not sure whether this is is the correct solution because previously it was working correctly with the same settings. But its microsoft so cant predict :)



anyways , those who have faced similar probs can try this and let us all know whether this solution worked ot not ....



regards

Vishal Dattani

vishal.dattani@gmail.com
Vishal Dattani
Friday, October 13, 2006 7:05:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thanks a lot. its working



The mistake i done is "i was renaming the virtual directory so visual

studio couldn't find the name."
mukeshsingh
Wednesday, October 25, 2006 10:53:00 PM (Mountain Standard Time, UTC-07:00)
Ok. It worked fine! Tks.
Thiago
Monday, October 30, 2006 2:55:00 AM (Mountain Standard Time, UTC-07:00)
hi thanks a lot for the suggestion. its working for me. It didnt work when i first deleted the VSWebCache, but when i modified the webinfo file path it worked.



Thanks again!!
Pratibha
Monday, November 27, 2006 8:20:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Fundooo.. It worked for me. Thanks!
anonymous rating
Tuesday, December 05, 2006 9:18:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
GREAT!!!
Felipe
Thursday, December 07, 2006 2:08:00 AM (Mountain Standard Time, UTC-07:00)
Great suggestion! This has fixed one of major issues in my apllication
Thursday, January 11, 2007 5:47:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thanks! Awesome!!!
Friday, January 19, 2007 5:05:00 PM (Mountain Standard Time, UTC-07:00)
I am using apache. instead of iis, i still have the problem..how can i configure the vs.net2003 for apache webserver?
kornel
Monday, January 29, 2007 2:46:00 PM (Mountain Standard Time, UTC-07:00)
Thanks for your help. It helped solve the problem on one computer. Still the other one is messy.

Vijay
Tuesday, February 06, 2007 6:53:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thanks a lot.
Nitin Kumar Gupta
Tuesday, February 13, 2007 8:05:00 PM (Mountain Standard Time, UTC-07:00)
I had this problem. It appeared after I added .htm extension to the application.

I removed extension and Studioloaded project. BUT I do not want to create an extension every time I need to work with project. Have anyone an idea how to add .htm extension to the application?

Cheers
Al Scull
Thursday, March 15, 2007 12:52:00 AM (Mountain Standard Time, UTC-07:00)
Hi all



I am trying to create a new web project in VS 2003.Net that runs on Apache 2.0.59 using mod_aspdotnet on Windows XP Home edition. But VS2003 is giving error



**************************************************************

Visual Studio .NET has detected that Webserver is running ASP.NET version 1.0



***************************************************************



However ASP.NET version 1.0 is not installed on the machine.



Please provide the inputs.



Thanks
Nitin
Thursday, March 15, 2007 1:42:00 PM (Mountain Standard Time, UTC-07:00)
Download 7 penis enlargement videos. User ratings & reviews of 55 penis enlargement pills.
Wednesday, April 04, 2007 4:28:00 AM (Mountain Standard Time, UTC-07:00)
Good Solution... Working for me.
Deepak
Sunday, April 08, 2007 1:43:00 AM (Mountain Standard Time, UTC-07:00)
I've encounter "The operation could not be completed" with Microsoft Environment Variables as the pop up box. I've done uninstalling vs.net, IIS. Install them again, deleting vswebcache, deleting temp folder under framework 1.1.4322 but nothing seems to be working.... I still see "The operation could not be completed" when i close my eye praying hard not to see it...
Bren
Tuesday, April 10, 2007 11:52:00 PM (Mountain Standard Time, UTC-07:00)
In my case I needed to do another thing to fix the "Visual Studio .NET cannot create or open the application" error.



It turned out that somehow read access got disabled in IIS virtual directory (only script execute was enabled).



Internet Service Manager -&gt; your app virtual directory -&gt; Properties -&gt; "Read" checkbox must be enabled.



I used Fiddler tool to peek in the communication between VS & IIS and to see what's wrong there.
atx
Wednesday, April 11, 2007 10:22:00 PM (Mountain Standard Time, UTC-07:00)
Great suggestion. Another to add to the list that need to be employed for various pitfalls that are encountered when sharing projects/solutions among developers.



In my particular case, this did not solve the issue.



The .csproj, .sln and and .webinfo files are straight forward for the most part. They use mostly relative paths for project info or standard .NET install paths. You can tell where some obvious configuration differences are between development environments. The binary .suo is a different animal. Not sure what's going on there. I appears the there are some user specific GUIDS that are utilized and some info not clearly visible in the .suo that are at the source of the problems.



Overall, you should be able to take a solution and/or project created somewhere else, but another user and relatively easily open it in another environement. If it can't find something specific, it should tell you what it can't find specifically. All I seem to get are non-specifc error messages that add absolutely no value.



Visual Studio Says: "Hey Mr. Developer. I can't find something. I'm not going to tell you what that something is, because that would make too much sense."



Visual Studio has some great features. However, there are some serious usability flaws in the architecture when it comes to:

a) Sharing project files among multiple developers who develop locally.

b) Setting up a local web development project in general. The IDE is too tightly integrated into IIS. Lots of configuration issues, etc. I understand the need for that for debugging, stepping through code, etc. But, you can't even start a Web project without it being tied to the Web server. You should be allowed to at least code and build/compile without jumping through a tremendous amount of hoops.



I constantly defend Microsoft products to peers compared to java, open source and Oracle. However, silly things that this that really shouldn't be an issue make it hard.



Another option: If you can open the project from a common Web server. You can use the copy project command available in the main menu. This will copy the project files to a local dev environment and make necessary configurations changes in the process which will allow the project to be opened locally. This doesn't always work, but like the solution above, works in some instances.



Brian
Monday, April 23, 2007 7:07:00 PM (Mountain Standard Time, UTC-07:00)
awesome .. thanks a lot :) It solved my problem
Sootanu
Monday, April 23, 2007 8:19:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Great....
Shaista
Tuesday, May 08, 2007 12:30:00 AM (Mountain Standard Time, UTC-07:00)
Hi,

First of all thank you for the all the details given above.

I am also getting the same problem but in a diff. scenario.



I am trying to run an application developed in .NET V1.0.

I have got 1.1 installed on my machine. i could load the application for the first time. i configured it right and it was running fine.

i closed the application.But when i tried to reload it, the problem started.

I tried all the solutions mentioned above. but in vain.

one more thing is, i was not able to delete the files from Temporary ASP.NET Files folder.

can anybody help me in this regard?



thanks in advance.



srinivas p





Srinivas
Tuesday, May 08, 2007 12:45:00 AM (Mountain Standard Time, UTC-07:00)
Srinivas,



If you create a new solution and add your web project to that solution does the problem go away? Is the .sln and/or the .suo file in source control? I've seen circumstances in which sharing an .sln file (even with just yourself) causes no end to headaches. The fix for me was to not have the VS.NET solution part of source control at all. I don't know if that addresses your issue, but I'd try recreating your solution to see if the issue goes away...or at least removing the project, exiting VS, reopening VS, and readding the project to the solution.
Tuesday, May 08, 2007 4:43:00 PM (Mountain Standard Time, UTC-07:00)
Hi,

thanks for the quick reply.

My code is not in source control. Is there anywy i can make it work without creating a new app and adding the webapp as it is a big app.



srinivas

srinivas
Tuesday, May 08, 2007 5:45:00 PM (Mountain Standard Time, UTC-07:00)
Hi Zupancic,



This is srinivas again. I resolved my problem by repairing my .Net installation. I repaired it and restarted my machine. Then i could load the web application.



Thank you once again. u ppl were of gr8 help.



Srinivas

srinivas
Friday, May 25, 2007 12:23:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thank you so much for providing this easy fix. I rate it as 5.0
RMP
Saturday, June 16, 2007 8:36:00 AM (Mountain Standard Time, UTC-07:00)
I am trying to find a link were I can download net v1.1.4322 can I get some help from you the link to go to or to were some-one can help me
David Bygrave
Saturday, June 16, 2007 1:13:00 PM (Mountain Standard Time, UTC-07:00)
I would wager that you already have the .NET Framework 1.1 installed on your computer, but this link may help:

http://msdn2.microsoft.com/en-us/netframework/aa569264.aspx#section3
Sunday, August 12, 2007 9:46:00 PM (Mountain Standard Time, UTC-07:00)
when I opened the Asp.Net application i got message like Visual Studio.Net cannot create or open the application. the likeliest problem is that the required component are not installed on the local web server. run the Visual Studio.Net setup & add the Web Development component.
Meghana
Thursday, August 23, 2007 1:58:00 AM (Mountain Standard Time, UTC-07:00)
Hi,

I am getting a problem on VS 2005 with Windows 2003 Server R2 while I am not able to get new web projects...



I know is something related to IIS Locking.



Any hints or url`s are very much useful...



Thanks in advance!



Agni.
Agni
Friday, September 14, 2007 10:32:00 PM (Mountain Standard Time, UTC-07:00)
The web server reported the following error when attempting to create or open the web project located at the following 'URL:http://local host/Webapplication1'. 'A connection with the server could not be established.'

Friday, September 14, 2007 10:46:00 PM (Mountain Standard Time, UTC-07:00)
setup cannot copy one or more files. The specific error code is '0x3e7'.Press ok to continue and Cancel to stop setup and try again.If you continue the components may not function properly.
Friday, September 14, 2007 10:52:00 PM (Mountain Standard Time, UTC-07:00)
file 'inetmgr could not find or spelling mistake.
Wednesday, January 16, 2008 6:22:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Excelent!
Tuesday, January 29, 2008 4:38:00 PM (Mountain Standard Time, UTC-07:00)
very good tip
satya
Monday, February 04, 2008 10:07:00 AM (Mountain Standard Time, UTC-07:00)
reinstsalling aspnet worked for me. thank you.
dings
Wednesday, March 05, 2008 10:04:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
deleting the folder worked for me - thank's a lot
anonymous rating
Monday, March 10, 2008 12:24:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thank you
Shankar
Monday, March 31, 2008 8:08:00 PM (Mountain Standard Time, UTC-07:00)
Thats Great! Solved my problem. Thanks so much
Bryan
Tuesday, April 08, 2008 6:53:00 PM (Mountain Standard Time, UTC-07:00)
This is great.It works 100%.

It fixed my problem.
Ajit kumar (Thomson Financial)
Tuesday, April 08, 2008 6:54:00 PM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Thsi is great.It fixed the issue.Thanks a lot.
Ajit Kumar
Tuesday, April 22, 2008 2:57:00 AM (Mountain Standard Time, UTC-07:00)
Nice post everyone - Looks like it is helping lots of peeps maintaining older 1.1 .net apps.



Unfortunately none of these worked for me.



The name of my Web Project was something like "USAX Web Project.csproj"



I renamed it to "USAX_Web_Project.csproj", updated the references in the .sln and .webinfo files (edit in notepad), cleared the various caches and then reopened the project. Bingo.



Maybe having spaces in the name honkered up the reference since it was trying to get to it via http://localhost/USAX(space)Web(space)Project.csproj.



Good luck!

Don

don schiavone
Thursday, April 24, 2008 3:47:00 PM (Mountain Standard Time, UTC-07:00)
Thanks. It fixed the issue
Ash
Tuesday, May 06, 2008 7:42:00 AM (Mountain Standard Time, UTC-07:00)
- rated a 5.
Wasted 1/2 a day on this, then I found your post!!! THANKS
Lisa
Name
E-mail
Home page

Comment (Some html is allowed: a@href@title, b, i, strike) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

Enter the code shown (prevents robots):

Live Comment Preview