Last post Apr 23, 2005 08:47 PM by mikeh36
Mar 25, 2005 10:55 PM|j.emmett|LINK
I keep trying to get DNN working on my home pc, (Windows XP Pro), and keep getting this error...
Access to the path "e:\inetpub\wwwroot\DotNetNuke\Portals\_default\Logs\LogConfig\LogConfig.xml.resources" is denied.
I have checked to make sure the ASPNET user has full control to the application and I have even tried every user on my system one by one, but with no luck. I was directed to look into the <processModel> section of the machine.config file, but do not know
what to look for. Also, this file resides in my "C" drive, would this make a difference?
Thank you much,
Mar 26, 2005 08:12 AM|j.emmett|LINK
It's me again, I have 36 seperate users / group accounts on my system and I have tried every last one of them and of course it does not work. The time it takes to get DNN installed and get all the settings figured out, ask questions in a forum and wait for
an answer, a developer could develop a custom site. I have installed DNN on 3 workstations and development server and all had major issues and now can not get DNN running on a simple home pc. I'm getting more convinced that DNN is not the way to go. Sorry
for the negative vibes, but it's just how I feel.
Mar 26, 2005 09:27 AM|Eppy|LINK
Mar 26, 2005 02:25 PM|j.emmett|LINK
my "C" drive holds primarily the OS. It is partitioned from an 80gig hard drive. So, my "D" drive is the rest of that hard drive, (70 gig), and I have a seperate 40 gig harde that is my "E" drive. My "E" drive is where I keep and do all my day-to-day stuff.
Mar 26, 2005 10:56 PM|xddg|LINK
Jim I want to tell you I cannot get it working locally any more - since 3.0.12 - No matter what I do, I can't. It's really been frustrating.
One of my good DNN friends Erik - put some small steps he found he needed to to get it working, which might help you. It got me closer, but I think it's somehow firewall related as I had that same error, but following his steps brought me closer to getting
it to work.
You can read here what he said in my blogs, but I know running the windows firewall meant I had to allow different IP addresses on our network, permission to view the DNN 2.1.2 installs.
I have every beta version working until 3.0.12 so am sure it's a permission thing/ firewall thing that once understood, won't be a problem any more.
Here's the link
Mar 26, 2005 11:50 PM|mikeh36|LINK
When you say home PC do you mean a home pc that's part of a network or a stand-alone system? From what I remember from the one time I tried it on a system that wasn't part of a network (vs a regular workgroup) it was a real PIA as the security settings really
don't work quite right. If it's on a system that's on a network then I'd double-check that the ASPNET user has permissions to the whole DNN folder. There's a chance you set the permissions on the parent folder and then didn't cascade them down to the rest
of the folders.
DNN is an excellent product and I'm sure once you can get it working you'll be more than happy with it.
Mar 27, 2005 01:15 AM|j.emmett|LINK
My home system is a stand alone system. Work of course is part of a domain. The home pc and work pc's both use Windows XP Pro for the OS. My work development server is a Windows Server 2003. The only system that is having a problem is the home pc. I have
looked at the blog entries and do not follow the steps that were given. I understand my frustration may have gotten the best me, I think we have all been there at one point or another.
Thank you much for all your help,
Mar 27, 2005 01:35 PM|mikeh36|LINK
Try checking this post. I think it'll help you with your home PC.
Mar 27, 2005 02:55 PM|j.emmett|LINK
thank you for the link, but that is one of the first things I do after installing Windows XP Pro on a pc. I should have mentioned that I do have the Security tab visible earlier, sorry. I have added and removed and re-added the ASP.NET machine account and
still no luck. This has got me baffled now [*-)]
Mar 27, 2005 03:46 PM|mikeh36|LINK
Well crap. [:(] I was hoping that would be the miracle fix for you. [;)]
I don't know if you answered this already but when you added the ASPNET machine account did the permissions cascade down to the rest of the directories? That usually tends to bite me in the backside when I setting security permissions.
Mar 27, 2005 07:33 PM|j.emmett|LINK
Yes. I even double checked before writing this, just to make sure. I checked all the way down to the actual xml resource file, and it has the 'full control' permission set for the ASPNET user and other users, too. This really has me stumped now. I have tried
resetting my pc after making a change, IIS resets, deleting cach and cookies and nothing seems to work. My concern at this point it not so much getting my system up and working, (though that would be nice), but what about the end user of the application? Does
this mean that users that have Windows XP can not view or use a web site that is on the DNN framwork??? That is now the question... It looks like we have something to investigate, I'm sure there is a way, it is just a matter of finding it [:D]
Mar 27, 2005 09:31 PM|ecktwo|LINK
Mar 27, 2005 10:19 PM|mikeh36|LINK
Since the problem file is located on drive E, did you also gave permission to E:\? yes the root.
That shouldn't be the cause of his problem but it might play a roll later on (ASPNET or at minimum Everyone) will need read on the root drive.
Jim, no worries about people with XP being able to view sites etc. I've never had a problem ever with that.
Mar 27, 2005 11:08 PM|ecktwo|LINK
Mar 27, 2005 11:09 PM|j.emmett|LINK
I have given the ASPNET full control on my "C", "D" and "E" drives, and no luck as of yet.
Mar 28, 2005 12:30 AM|j.emmett|LINK
ok, tried that, no luck, but thank you for the tip. I re-created everything... started from scratch, (again). This time I think there is some progress, well... at least there is a different error. Now I am recieving this error message...
The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist.
I have reset IIS, deleted the database, cleared cookies and cach, and started completely over several times, but still no luck. But, it is not the permission error [:D], at least we have overcame that one.
Thank you much guys and gals for all the help. I do appreciate it!
Mar 28, 2005 10:52 AM|roarstudios|LINK
Mar 31, 2005 01:48 PM|Higez|LINK
I am running DNN 3.0.12 on a WIN XP machine (DNN2 was running good on the same machine!) and I have tried all the things said in this forum but no matter what I do I'm still getting the message:
Can you give me some other hints???
Mar 31, 2005 02:40 PM|j.emmett|LINK
actually, I have not been able to get DNN 3.0.12 working on a stand alone Windows XP Pro computer. I have had no problems when the pc is within a domain, though. I will be happy to review your connection if you would post, an extra set of eyes never hurts,
Mar 31, 2005 04:00 PM|Higez|LINK
Earlier I posted a problem with DNN 3.0.12 on WIN XP:
I found the solution of that problem on the internet:
SQL Enterprise Manager right click your
server to get the
Select the security tab and switch authentication to "Sql
Windows", restart the service or better yet restart the whole
Once that problem was solved, I 'm having another problem:
DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )
ERROR: Could not connect to database.
The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist.
So my DNN 3.0.12 still isn't working ....
Mar 31, 2005 04:33 PM|xddg|LINK
Jim, I cannot get working and I'm testing another build as well.. I've tried localhost/, I've tried putting the dotnetnuke.loc as advised by one of my colleagues.
Someone has said installed 3.0.11 and see if you can upgrade.. So I will try that now, but for me, it's no changed the whole dynamics on how I have to work.. I even wrote about it in my blogs.. I'm a bit annoyed, but not many others seem to have this problem,
and no other core team members, so its' regarded as a one off instance..
For the records, I cannot use Friendly urls live any more either - something must have changed, but again, because I'm in such a minority - it's one those things that they can't stop the releases from happening becuase it's such an isolated incident ..
I am extremely frustrated with this this - now I cannot test locally any more, and have to setup build after build live, just to do my developement work. GRRRR.
So you're not on your own and I'm still chipping away at it.
Mar 31, 2005 05:00 PM|Higez|LINK
MY DNN 3.0.12 IS WORKING!!!!
My latest problem was: "The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist."
So I typed
http://localhost/DotNetNuke/Install/Install.aspx?mode=Install and then the installation was running perfect without any problem.
Finally I can begin with the real work in DNN 3.0.12.
Mar 31, 2005 05:04 PM|j.emmett|LINK
Hi Nina and Hilde,
The error that Hilde has is where I am, too. I have not been able to get around it. I do appreciate everyone looking into this. I do not know about the isolated incidents, though. We have three right here in this post alone. I have tried the 3.0.11 to 3.0.12
upgrade already on my system and of course had no success.
I do have one off the topic question... has anyone tried to use DNN on AOL, Netscrape 4.x or 6.x??? I have a client that wants the browser compatibilities back to Netscrape 4.7!!!
Thank you much all,
Mar 31, 2005 05:14 PM|mikeh36|LINK
A couple of things. Can you connect to the database via Query Analyzer using the same credentials as you used in your connection string? If yes then carry on. If not then figure that part out (I think you can but I'm not positive judging
by the error message you posted).
The next thing to look at (and this might help you too Jim) is in the Installation folder of your DNN install. From reading the installation guide in the Documents folder, the problem stems from the aborted install earlier. What happens
is that a file called dnn.config is created with the database version during the install process. DNN checks that file versus the version that's stored in the database and if they're the same then it doesn't fire the install scripts. Hence the error that you're
getting. Supposedly you can just delete that file and the next time you fire up the site it'll run the install scripts. In that same document it lists changes that can be done to your web.config to force an update as well.
Mar 31, 2005 05:30 PM|Higez|LINK
Jim and Mike
Meanwhile I posted a reply that I was able to make my DNN 3.0.12 running! You can read what I have done to make it work in my reply.
I am so happy and I wish to thank you very much for the reactions and support!
PS Sorry for my "dictionary English", but it's not my native language...
Mar 31, 2005 05:56 PM|j.emmett|LINK
That is GREAT Hilde [:D]
As soon as I get home from work, I will try the same thing, (hope to get the same results).
And, no reason to apologize for your dictionary English, you know a lot more than people who do have English as their native language.
And I agree, the support out here is great! I know I get frustrated and end up typing it out sometimes, (sorry folks), but people from all parts of the world still put up with me and help out where they can. The words "Thank you" seems to small sometimes,
so hopefully it will be enough. And on that note...
Thank You All,
Mar 31, 2005 09:23 PM|j.emmett|LINK
Holy Portal Batman, we have a working DNN [:D]
Well, hats off to everyone and Hilde's last stand before changing careers worked. I had to do a little more tweaking, but after all the tweaks the
http://localhost/DotNetNuke/Install/Install.aspx?mode=Install was the ticket. It did not work for me the first time around like I said, got the cool looking DNN install page and then
a cool looking DNN error page [:'(] So, back to more tweaking and then typed that URL in again and it did it's thing.
Now the sad thing is I have no excuse to not develop from home, too. [8-|]
Apr 03, 2005 01:46 PM|Higez|LINK
That's fantastic news!!! It's a wonderfull feeling to get that DNN3 working after all these problems.
Now we can begin with the skinning part ... from home.
Apr 05, 2005 10:19 PM|xddg|LINK
Ok - I FINALLY FINALLY have got DNN 3.0.13 installed on my server.. LOCALLY -
I don't know why, however when I looked at the web.config file, there were a few differences in there, but this is how I did it..
Installed the latest version I knew worked... eg.. 3.0.11 - a clean install, looked perfect, then I copied the 3.0.12files, but had done a copy of the line which had the database connections, then pasted into the new web.config file. Then repeated for the
One thing that does happen someteims is that there are some errors which I cycled through, and then it did the installation.
If there are bugs in the upgrade path, I'll have to wear them I guess, I'm not sure, but all I can say is that I AM HAPPY .. there was a solution.
It just makes working so much handier.. [:D][:D][:D]
Apr 06, 2005 12:06 AM|j.emmett|LINK
That is great to hear Nina, we all seem to have benifitted from this post [:D] Now I have to work on the skinning. Nina, skinning is right up your alley, isn't it??? I'm open for ideas, tips, triks, the whole nine yards. I have not developed a skin before
[:(], so any help would be greatly appreciated.
Apr 21, 2005 10:21 PM|Girlnet|LINK
Apr 21, 2005 10:26 PM|Girlnet|LINK
Apr 21, 2005 11:43 PM|xddg|LINK
Hi GirlNet - Did you try to install an earlier version and upgrade?
I noticed you didn't make any comments about this.
Apr 23, 2005 12:30 AM|mikeh36|LINK
Hmmm, I coulda swore I replied to this last night.
Girlnet, what error are you getting? There's quite a few of them listed in this thread.
Apr 23, 2005 09:25 AM|Girlnet|LINK
I see the recommendation is to do 3.0.12 and upgrade? I'll give that a try. I'm not running it on an XP system - 2000 Advanced Server. I had to rebuild because of 46 viruses, and it seems I've done a million installs of DNN. I jumped on this bandwitch
at v2. But doing a fresh install of 3.0.13 just kicked my butt!
I'll let you know if that worked.
Apr 23, 2005 10:55 AM|mikeh36|LINK
Apr 23, 2005 07:19 PM|Girlnet|LINK
Of course I gave the ASPNET user all the appropriate rights - but maybe the issue I was having was my server was a domain controller. I ended up demoting it, reinstalling iis and framework. I started with a fresh 3.0.12 to upgrade to 3.0.13 and it's working
now. Now comes the fun part of piecing everything back together.
Apr 23, 2005 08:47 PM|mikeh36|LINK