RE: OSD Image Installation fails - Can't find DP
- From: "Steve Mc" <SteveMc@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 17 Jan 2006 13:15:02 -0800
I saw a thread that showed how to troubleshoot conenctin to unc by using the
osdConnectToUNCpath.exe. i tried this and got the following errors according
to the log. Hopefully this is helpful. Apparently gets an error decrypting
the credentials:
<![LOG[Running osdConnectToUNC]LOG]!><time="15:52:01.103+000"
date="01-17-2006" component="osdConnectToUNC" context="" type="1"
thread="1236" file="osdconnecttounc.cpp:120">
<![LOG[Initializing COM Library]LOG]!><time="15:52:01.113+000"
date="01-17-2006" component="osdConnectToUNC" context="" type="1"
thread="1236" file="osdconnecttounc.cpp:125">
<![LOG[Initializing COM Security]LOG]!><time="15:52:01.123+000"
date="01-17-2006" component="osdConnectToUNC" context="" type="1"
thread="1236" file="osdconnecttounc.cpp:132">
<![LOG[CHECK FAILED: wcslen(pszKey) == (21 * 2) (Error =
80070057)]LOG]!><time="15:52:01.144+000" date="01-17-2006"
component="osdConnectToUNC" context="" type="3" thread="1236"
file="cryptohelper.cpp:89">
<![LOG[Invalid parameter: wcslen(pszKey) == (c_uCryptoKeyLength *
2)]LOG]!><time="15:52:01.154+000" date="01-17-2006"
component="osdConnectToUNC" context="" type="3" thread="1236"
file="cryptohelper.cpp:89">
<![LOG[CHECK FAILED: DecryptString(sUsername, pszKey, 0x00) (Error =
80070057)]LOG]!><time="15:52:01.154+000" date="01-17-2006"
component="osdConnectToUNC" context="" type="3" thread="1236"
file="cryptohelper.cpp:177">
<![LOG[CHECK FAILED: DecryptCredentials( sUserName, sPassword, sKey.c_str()
) (Error = 80070057)]LOG]!><time="15:52:01.154+000" date="01-17-2006"
component="osdConnectToUNC" context="" type="3" thread="1236"
file="osdconnecttounc.cpp:83">
<![LOG[Error decrypting Access credentials to connect to the UNC Path. Code
0x80070057]LOG]!><time="15:52:01.154+000" date="01-17-2006"
component="osdConnectToUNC" context="" type="3" thread="1236"
file="osdconnecttounc.cpp:83">
<![LOG[CHECK FAILED: RunConnectToUNCPath(argc, pszaArgs) (Error =
80070057)]LOG]!><time="15:52:01.154+000" date="01-17-2006"
component="osdConnectToUNC" context="" type="3" thread="1236"
file="osdconnecttounc.cpp:148">
"Steve Mc" wrote:
> Our OSD environment was working about a month ago. I am not certain, but the
> server team put SP1 on the server that hosts SMS and it seemed to not work
> around that time.
> Our main SMS server is also the MP and DP and we have one primary site.
>
> When booting to the image installation cd (this is how we do all of the
> installs right now, although it will also fail if pushed through SMS), When a
> package is selected and a computer name is specified, the install fails..
>
> "could not connect to the installation package on..... An extended error has
> occured (800704B8)"
>
> According to OSDInstallWizard.log the packag location it is trying use is
> correct and I can ping it by just using the server name. I get an failure in
> the log:
>
> [Failed to connect to <server path> (1208) retry in 10 Seconds]
> [Failed to connect to <server path> (1208) retry in 20 Seconds]
> .
> .
> [Client status handler is not available. no Status will be sent]
>
> If I manually install from a different location and supply different
> credentials , I can get it to work if I use the package share location
> (SMSPKGE$). Make me think it is an issue with the credentails the CD is
> using in the ripinfo.ini
>
> Could Server 2003 SP1 (not SMS SP1) have changed anything that would mess
> this up? The access accounts have not changed (that I know of), and I have
> tried new images and multiple CDs.
>
.
- Prev by Date: Re: OSD dosnt work with CISCO DHCP and VLANs
- Next by Date: Re: OSD dosnt work with CISCO DHCP and VLANs
- Previous by thread: Re: OSD dosnt work with CISCO DHCP and VLANs
- Next by thread: OSD loadstate fails Error 1008 reported by USMT
- Index(es):
Relevant Pages
|
