Tags: 0x00000005, acomputer, code, error, failed, installing, isnetresourceaccessible, microsoft, msdn, offices, ran, server, sms2003, software, sp2
IsNetResourceAccessible failed with error code 0x00000005
On Microsoft » Microsoft Server
6,692 words with 2 Comments; publish: Wed, 04 Jun 2008 02:17:00 GMT; (300109.38, « »)
I ran into a problem the other day, installing XP SP2 with SMS2003 on a
computer in one of my outer offices. It failed with an error 1603 which I'm
sure was because the Windows Installer had an issue. But I've noticed that
many of the Advertisements I do in these outer offices have the same error
line in the execmgr.log,
IsNetResourceAccessible failed with error code 0x00000005
Every time, except with XP SP2, the install goes fine and after the above
line, with my XP install it showed:
Rolling over to network access account to check content location
Successfully selected content location \\OCDASOC000\SMSPKGD$\DA100039
Executing program as a script
Successfully prepared command line
"\\OCDASOC000\SMSPKGD$\DA100039\update\update.exe" /q /f /forcerestart
Command line = "\\OCDASOC000\SMSPKGD$\DA100039\update\update.exe" /q /f
/forcerestart, Working Directory = \\OCDASOC000\SMSPKGD$\DA100039\
Created Process for the passed command line
Raising event:........
Raised Program Started Event for Ad:DA120264, Package:DA100039, Program:
Automated upgrade from XP or XPSP1
Program exit code 1603
I think in this SP2 case, the machine may have had a Windows Installer error
which threw the error, however I can't figure out why every advertisent logs
the
IsNetResourceAccessible failed with error code 0x00000005 error. I'm using
Advanced Security on my site and my adverts run with admin rights. Is this
nothing to worry about or should I be concerned?
Sandy Wood
Orange County District Attorney
http://ms-server.itags.org/q_microsoft-server_64340.html
All Comments
Leave a comment...
- 2 Comments
- Hi Sandy,
The error that you are seeing is a normal error. When running in Admin mode
the program will be running in SYSTEM context. Thus when it tries to access
the DP it will do so with the machine account. The machine account does not
have access to the DP so it simply rolled over to the Network Access
Account. This is how it is designed.
As for the 1603 error. This is a very generic "something went wrong" error
from Windows Installer.
Thanks
Scott Brimley [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Additional Resources:
SMS 2.0 Resource Page:
http://www.microsoft.com/technet/pro...2/default.mspx
SMS 2003 Resource Page:
http://www.microsoft.com/technet/pro...3/default.mspx
SMS 2003 Technical FAQ:
http://www.microsoft.com/technet/pro...q/default.mspx
Scripts: http://www.microsoft.com/technet/scr...s/default.mspx
"Sandy Wood" <sandy.wood.ms-server.itags.org.nospam.com> wrote in message
news:D1B171A1-82B5-44F9-9A0D-A0435F98DC9B.ms-server.itags.org.microsoft.com...
>I ran into a problem the other day, installing XP SP2 with SMS2003 on a
> computer in one of my outer offices. It failed with an error 1603 which
> I'm
> sure was because the Windows Installer had an issue. But I've noticed that
> many of the Advertisements I do in these outer offices have the same error
> line in the execmgr.log,
> IsNetResourceAccessible failed with error code 0x00000005
> Every time, except with XP SP2, the install goes fine and after the above
> line, with my XP install it showed:
> Rolling over to network access account to check content location
> Successfully selected content location \\OCDASOC000\SMSPKGD$\DA100039
> Executing program as a script
> Successfully prepared command line
> "\\OCDASOC000\SMSPKGD$\DA100039\update\update.exe" /q /f /forcerestart
> Command line = "\\OCDASOC000\SMSPKGD$\DA100039\update\update.exe" /q /f
> /forcerestart, Working Directory = \\OCDASOC000\SMSPKGD$\DA100039\
> Created Process for the passed command line
> Raising event:........
> Raised Program Started Event for Ad:DA120264, Package:DA100039, Program:
> Automated upgrade from XP or XPSP1
> Program exit code 1603
> I think in this SP2 case, the machine may have had a Windows Installer
> error
> which threw the error, however I can't figure out why every advertisent
> logs
> the
> IsNetResourceAccessible failed with error code 0x00000005 error. I'm using
> Advanced Security on my site and my adverts run with admin rights. Is this
> nothing to worry about or should I be concerned?
> --
> Sandy Wood
> Orange County District Attorney
#1; Wed, 04 Jun 2008 02:18:00 GMT
- Scott,
Thanks very much for the info. I feel much better and am better informed also!
Sandy Wood
Orange County District Attorney
"Scott Brimley [MSFT]" wrote:
> Hi Sandy,
> The error that you are seeing is a normal error. When running in Admin mode
> the program will be running in SYSTEM context. Thus when it tries to access
> the DP it will do so with the machine account. The machine account does not
> have access to the DP so it simply rolled over to the Network Access
> Account. This is how it is designed.
> As for the 1603 error. This is a very generic "something went wrong" error
> from Windows Installer.
> --
> Thanks
> Scott Brimley [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Additional Resources:
> SMS 2.0 Resource Page:
> http://www.microsoft.com/technet/pro...2/default.mspx
> SMS 2003 Resource Page:
> http://www.microsoft.com/technet/pro...3/default.mspx
> SMS 2003 Technical FAQ:
> http://www.microsoft.com/technet/pro...q/default.mspx
> Scripts: http://www.microsoft.com/technet/scr...s/default.mspx
> "Sandy Wood" <sandy.wood.ms-server.itags.org.nospam.com> wrote in message
> news:D1B171A1-82B5-44F9-9A0D-A0435F98DC9B.ms-server.itags.org.microsoft.com...
>
>
#2; Wed, 04 Jun 2008 02:19:00 GMT