NEWA not working on Win 8.1

[dshoup]

I recently updated from Win 7 to Win 8.1. I'm not sure if it is related or not, but I get an error when I try to use NEWA (even using localhost with a port number on my nPVR computer). The error is:

Server Error in '/' Application.

The current identity (NT AUTHORITY\SYSTEM) does not have write access to 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The current identity (NT AUTHORITY\SYSTEM) does not have write access to 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[HttpException (0x80004005): The current identity (NT AUTHORITY\SYSTEM) does not have write access to 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files'.]
System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +700
System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException) +231

[HttpException (0x80004005): The current identity (NT AUTHORITY\SYSTEM) does not have write access to 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files'.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +554
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +95
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +449

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34009

I've tried stopping my firewall and re-installing NEWA again using the development build on the web site. Anyone have suggestions on what to try next?

[dshoup]

I think my problem is the same one described at http://forums.nextpvr.com/showthread.php...indows-8-1. I'll reply there and we can essentially merge these two together...I just thought I should post here so anyone searching the forum in the future will get directed there.

[dshoup]

Sub, you commented in the other thread that you did not think it was related to that thread, so I'll follow up here. You suggested I stop the recording service and run "nrecord.exe RUN" from the command prompt (started with 'Run As Administrator') to see if that works. It did work. I received a firewall alert, which I told it to allow, but then it worked fine. I then rebooted my computer to see if it would work when it loads nrecord as a part of booting windows. It did not. I again stopped the recording service and ran the nrecord.exe RUN as administrator and it worked with no firewall prompt. So, I suspect it has something with needing administrator rights when trying to start the service? If so, how do I deal with that so the NEWA works when the computer reboots?

[mvallevand]

What user is the Recording Service running as? "Local System" is the default.

Martin

[sub]

Sub, you commented in the other thread that you did not think it was related to that thread, so I'll follow up here. You suggested I stop the recording service and run "nrecord.exe RUN" from the command prompt (started with 'Run As Administrator') to see if that works. It did work. I received a firewall alert, which I told it to allow, but then it worked fine. I then rebooted my computer to see if it would work when it loads nrecord as a part of booting windows. It did not. I again stopped the recording service and ran the nrecord.exe RUN as administrator and it worked with no firewall prompt. So, I suspect it has something with needing administrator rights when trying to start the service? If so, how do I deal with that so the NEWA works when the computer reboots?

The default 'localsystem' account has been fine for everyone else, so it must be something permissions or firewall related about the config of your machine. Unfortunately i'm not sure exactly what that'd be though.

[dshoup]

Bummer. Sub, Can you briefly explain what the command you had me run is doing...it appears I have to keep the command prompt window open for this to keep working...is that correct?

Can anyone think of a way around this? Here are some extra things I have tried, but none have helped:

1. right-clicked Nrecord.exe and selected properties and selected "run this program as an administrator" on the compatibility tab.

2. set up the C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary\ as a shared folder with read and right access granted to "everyone." However, I know this was useless as I still get a prompt to allow administrator rights if I try to copy a file to this directory and trying to save a word document there simply fails with no option to escalate rights.

I guess I may have to give up on this, but if anyone has any suggestions I'd love to hear them.

[mvallevand]

Did you check the permissions for the recording service as I asked? If it is "Local System" you might be able to change it to Administrator

You don't want to use NRecord RUN try to find the cause.

Martin

[dshoup]

mvallevand, can you elaborate a bit? I did the default install of nPVR, so I suspect that means it is local (and it is located in the \users\public folder rather than user\MyUserName folder. How would I go about changing this?

[mvallevand]

In Administrative Tools-> Services you will find the NPVR Recording Service, right click for properties, and it's on the Log On tab.

Martin

[sub]

Bummer. Sub, Can you briefly explain what the command you had me run is doing...it appears I have to keep the command prompt window open for this to keep working...is that correct?

That was just a check to see if you got any firewall popups or similar. It's effectively running the service from your desktop so we could see anything that popped up. You wouldn't want to run it that way long term.

The fact it's running fine that way, tells us it's just something about your account or permissions or firewall that is stopping it running as a service. Not clear exactly what though.