This error looks like the one I was getting when I was first figuring the required folder permissions.  You are most likely getting this error because the portal did not install.  Use your ftp program and check the portal folder.  There should be two folders within it to start, one named default and the other is 0.  If you don't see folder 0 then the security permissions for the virtual folder may not have stuck when you applied them. 

The first couple of times that I applied folder permission on Go Daddy I didn't do the confirm from the edit screen.  When you create the folder you assign permissions, and it then goes to the edit screen.  If you don't apply the settings there too they don't seem to stick.

Thanks for the heads up. I will check it out. In the mean time, for anyone that is still interested I figured out what the problem was finally. When setting up the portals folder in GoDaddy you must use the same capitalization as the portals folder you upload. In the package I downloaded from Michael's site portals was spelled with a lower case p. When I changed the capitalization to match everything installed flawlessly. I think I read somewhere earlier in the thread that capitalization didn't matter, but in my case it seems to have made all the difference.

Good luck to everyone else.

Your information is incorrect.  The fact that you refer to this thread in yours as "an example" shows that your information is incorrect as well as the number of people that have successfully setup a site.  The discussion you refer to by the Core team member is made before I took the time to figure out the required settings to make the site stable and refers to a straight install using the installation package without any other user interaction.  The other issues are refered to are in 4.0 and have been dealt with in the more recent releases.The virtual folder settings with the proper permissions makes the site stable.  Go Daddy even offers the 4.02 now in their site setups.