BDD - ZTI.vbs error -2147467259 when connecting to AdminDB under WinPE

G

Guest

We are currently using BDD 2.5 ent and have a situation where our
"refresh" is working but our "bare metal" isn't.

When booting under WinPE the OSD Deployment CD fails to connect to the
SQL AdminDB and a number of installation parameters (ComputerName)
aren't populated as a result.

The ADO error isn't very specific, which doesn't help things. We've
tried both our own WinPE image and the OSD supplied one and get the
same results.

Is anyone able to shed some light on the cause of the problem. Michael
N.?

Regards
Rob

Log from successful refresh
===========================================================
CHECKING the [BDDDB] section
Using from [BDDDB]: SQLServer = xxxxxx
Using from [BDDDB]: Database = BDDAdminDB
Using from [BDDDB]: Table = BDDAdminCore
Using from [BDDDB]: StoredProcedure = BDDAdminCore
Warning - DBID key not defined in the section [BDDDB]
Warning - DBPwd key not defined in the section [BDDDB]
Using from [BDDDB]: SQLShare = BDDLogs
Already connected to server xxxxxx as it is the current distribution
point.
OPENING TRUSTED SQL CONNECTION to server xxxxxx and database
BDDAdminDB.
Successfully opened connection to database.
About to issue SQL statement: SELECT * FROM BDDAdminCore WHERE
MACADDRESS IN ('XX:xx:xx:xx:xx:xx')
Successfully queried the database.

Log from unsuccessful bare metal
===========================================================
CHECKING the [BDDDB] section
Using from [BDDDB]: SQLServer = xxxxx
Using from [BDDDB]: Database = BDDAdminDB
Using from [BDDDB]: Table = BDDAdminCore
Using from [BDDDB]: StoredProcedure = BDDAdminCore
Warning - DBID key not defined in the section [BDDDB]
Warning - DBPwd key not defined in the section [BDDDB]
Using from [BDDDB]: SQLShare = BDDLogs
Already connected to server xxxxx as it is the current distribution
point.
OPENING TRUSTED SQL CONNECTION to server xxxxx and database BDDAdminDB.
ZTI error opening SQL Connection: Unspecified error (-2147467259)
ADO error: Unspecified error (Error #-2147467259; Source: Provider; SQL
State: ; NativeError: -2147467259)


CustomerSettings.ini
==================================================
[BDDDB]
SQLServer=xxxxxx
Database=BDDAdminDB
Table=BDDAdminCore
Parameters=MacAddress
StoredProcedure=BDDAdminCore
SQLShare=BDDLogs
 
M

Michael Niehaus [MS]

Can you provide the full log? The BDD script should have attempted to make
a secure connection to the SQL Server using OSDConnectToUNC.exe and logged
the result. If that fails, you won't be able to make a named pipe
connection to the SQL Server (required to connect to the SQL DB).

-Michael Niehaus
Systems Design Engineer
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
 
G

Guest

Hi Michael,

Here's the log and customsettings.ini. I'm of the thinking that MDAC
is having trouble running from the read only media. The same
OSDWinPE.wim works under Refresh, with the exception the local
administrator group, isn't populated.

I can post the Refresh log if it will help.

Regards
Rob

-------------------------- PHASE START ---------------------------
Using COMMAND LINE ARG: Debug = True
Using COMMAND LINE ARG: Phase = PREINSTALL
Using DEFAULT VALUE: Ini file =
\\XXXXSMS00\SMSPKGE$\WV100055\CustomSettings.ini
Using DEFAULT VALUE: CapiComDLL =
\\XXXXSMS00\SMSPKGE$\WV100055\capicom.dll
Using LOGFILE = C:\MININT\SMSOSD\OSDLOGS\zerotouchinstallation.log
OSD environment is available.
Warning - Unable to retrieve WMI object: ActiveX component can't create
object (429)
------------------------- Initialization -------------------------
Operating System = WinPE
Is a server OS = False
Warning - Unable to obtain HAL information since WMI is unavailable.
Host name = MININT-TG29RJ13
Warning - Unable to obtain asset details (asset tag, serial number,
make, model, product, UUID) since WMI is unavailable.
MAC address = 00:14:C2:CC:B4:33
Default Gateway = 10.35.64.1
SMS distribution point = XXXXSMS00
Using ScanStateArgs = /i:miguser.inf /i:migapp.inf /i:migsys.inf
/i:sysfiles.inf /i:updateuser.inf /i:userdata.inf /v:7 /x /s /f /o /c
Using LoadStateArgs = /v:7 /c
Checking Windows PE to make sure necessary MDAC DLLs are in place.
WARNING - Named pipe library DBNMPNTW.DLL not found in Windows PE and
cannot be copied (PE not running from hard drive)
Windows PE check complete.
Using from [Settings], CustomKeysUserData: CustomKey = UDSHARE, current
value =
Using from [Settings], CustomKeysUserData: CustomKey = UDDIR, current
value =
Using from [Settings], CustomKeysUserData: CustomKey = UDPROFILES,
current value =
Using from [Settings], CustomKeysUserData: CustomKey = SLSHARE, current
value =
Using from [Settings], CustomKeysUserData: CustomKey = OSINSTALL,
current value =
Using from [Settings], CustomKeysUserData: CustomKey = PACKAGES,
array.
Using from [Settings], CustomKeysUserData: CustomKey = ADMINISTRATORS,
current value =
Using from [Settings], CustomKeysUserData: CustomKey = DRIVERPATH,
current value =
Using from [Settings], CustomKeysUserData: CustomKey = POWERUSERS,
array.
Using from [Settings], CustomKeysSysprep: CustomKey = COMPUTERNAME,
current value =
Using from [Settings], CustomKeysSysprep: CustomKey = TIMEZONE, current
value =
Using from [Settings], CustomKeysSysprep: CustomKey = JOINDOMAIN,
current value =
Using from [Settings], CustomKeysSysprep: CustomKey = MACHINEOBJECTOU,
current value =
Using from [Settings], OSDVariableKeys: CustomKey = OSDINSTALLSILENT,
current value =
Using from [Settings], OSDVariableKeys: CustomKey = OSDINSTALLPACKAGE,
current value =
Using from [Settings], OSDVariableKeys: CustomKey = OSDINSTALLPROGRAM,
current value =
Using from [Settings], OSDVariableKeys: CustomKey = OSDNEWMACHINENAME,
current value =
----------------------- End Initialization -----------------------
Using from [Settings]: SearchPriority = MODEL, DEFAULTGATEWAY, SQL,
DEFAULT
------ Processing the [] section ------
------ Processing the [DEFAULTGATEWAY] section ------
Match found for default gateway 10.35.64.1, retrieving settings.
------ Processing the [SiteA] section ------
CHECKING the [BDDDB] section
Using from [BDDDB]: SQLServer = XXXXSMS00
Using from [BDDDB]: Database = BDDAdminDB
Using from [BDDDB]: Table = BDDAdminCore
Using from [BDDDB]: StoredProcedure = BDDAdminCore
Warning - DBID key not defined in the section [BDDDB]
Warning - DBPwd key not defined in the section [BDDDB]
Using from [BDDDB]: SQLShare = BDDLogs
Already connected to server XXXXSMS00 as it is the current distribution
point.
OPENING TRUSTED SQL CONNECTION to server XXXXSMS00 and database
BDDAdminDB.
ZTI error opening SQL Connection: Unspecified error (-2147467259)
ADO error: Unspecified error (Error #-2147467259; Source: Provider;
SQL State: ; NativeError: -2147467259)
Using from [SiteA]: UDSHARE = \\XXXXSMS00\MigData
Using from [SiteA]: SLSHARE = \\XXXXSMS00\BDDLogs
Using from [SiteA]: ADMINISTRATORS = XXXX\DLG-CISSOELOCALADMIN
------ Processing the [SQL] section ------
------ Processing the [DEFAULT] section ------
Using from [DEFAULT]: UDDIR = %OSDCOMPUTERNAME%
Using from [DEFAULT]: UDPROFILES = *\*
Using from [DEFAULT]: OSINSTALL = Y
Using from [DEFAULT]: COMPUTERNAME = %OSDNEWMACHINENAME%
Using from [DEFAULT]: TIMEZONE = 250
Using from [DEFAULT]: JOINDOMAIN = XXXX
Using from [DEFAULT]: MACHINEOBJECTOU = OU=YYYY
Computers,DC=XXXX,DC=aa,DC=bbb,DC=au
Using from [DEFAULT]: OSDINSTALLSILENT = 1
------ Done processing CustomSettings.ini ------
No values found for PACKAGES
Unable to determine value for DRIVERPATH
No values found for POWERUSERS
Unable to determine value for OSDINSTALLPACKAGE
Unable to determine value for OSDINSTALLPROGRAM
Unable to determine value for OSDNEWMACHINENAME
Even after all search criteria were processed, some values could not be
determined.
Already connected to server XXXXSMS00 as it is the current distribution
point.
ZTI script starting processing for PREINSTALL phase.
Updating OSD Shared memory with UDSHARE=\\XXXXSMS00\MigData
Updating OSD Shared memory with UDDIR=%OSDCOMPUTERNAME%
Updating OSD Shared memory with UDPROFILES=*\*
Updating OSD Shared memory with SLSHARE=\\XXXXSMS00\BDDLogs
Updating OSD Shared memory with OSINSTALL=Y
Updating OSD Shared memory with
ADMINISTRATORS=XXXX\DLG-CISSOELOCALADMIN
Not updating OSD Shared memory with blank value for DRIVERPATH
Updating OSD Shared memory with COMPUTERNAME=%OSDNEWMACHINENAME%
Updating OSD Shared memory with TIMEZONE=250
Updating OSD Shared memory with JOINDOMAIN=XXXX
Updating OSD Shared memory with MACHINEOBJECTOU=OU=YYYY
Computers,DC=XXXX,DC=aa,DC=bbb,DC=au
Updating OSD Shared memory with OSDINSTALLSILENT=1
Not updating OSD Shared memory with blank value for OSDINSTALLPACKAGE
Not updating OSD Shared memory with blank value for OSDINSTALLPROGRAM
Not updating OSD Shared memory with blank value for OSDNEWMACHINENAME
Updating OSD Shared memory with ZTISettings=1

ZTI PREINSTALL processing completed successfully.
Copying local logfile
(C:\MININT\SMSOSD\OSDLOGS\zerotouchinstallation.log) to
\\XXXXSMS00\BDDLogs\.log
-------------------------- PHASE START ---------------------------
Using COMMAND LINE ARG: Debug = True
Using COMMAND LINE ARG: Phase = POSTINSTALL
Using DEFAULT VALUE: Ini file =
\\XXXXSMS00\SMSPKGE$\WV100055\CustomSettings.ini
Using DEFAULT VALUE: CapiComDLL =
\\XXXXSMS00\SMSPKGE$\WV100055\capicom.dll
Using LOGFILE = C:\MININT\SMSOSD\OSDLOGS\zerotouchinstallation.log
OSD environment is available.
Warning - Unable to retrieve WMI object: ActiveX component can't create
object (429)
------------------------- Initialization -------------------------
Operating System = WinPE
Is a server OS = False
Warning - Unable to obtain HAL information since WMI is unavailable.
Host name = MININT-TG29RJ13
Warning - Unable to obtain asset details (asset tag, serial number,
make, model, product, UUID) since WMI is unavailable.
MAC address = 00:14:C2:CC:B4:33
Default Gateway = 10.35.64.1
SMS distribution point = XXXXSMS00
Using ScanStateArgs = /i:miguser.inf /i:migapp.inf /i:migsys.inf
/i:sysfiles.inf /i:updateuser.inf /i:userdata.inf /v:7 /x /s /f /o /c
Using LoadStateArgs = /v:7 /c
Using from [Settings], CustomKeysUserData: CustomKey = UDSHARE, current
value = \\XXXXSMS00\MigData
Using from [Settings], CustomKeysUserData: CustomKey = UDDIR, current
value = %OSDCOMPUTERNAME%
Using from [Settings], CustomKeysUserData: CustomKey = UDPROFILES,
current value = *\*
Using from [Settings], CustomKeysUserData: CustomKey = SLSHARE, current
value = \\XXXXSMS00\BDDLogs
Using from [Settings], CustomKeysUserData: CustomKey = OSINSTALL,
current value = Y
Using from [Settings], CustomKeysUserData: CustomKey = PACKAGES,
array.
Using from [Settings], CustomKeysUserData: CustomKey = ADMINISTRATORS,
current value = XXXX\DLG-CISSOELOCALADMIN
Using from [Settings], CustomKeysUserData: CustomKey = DRIVERPATH,
current value =
Using from [Settings], CustomKeysUserData: CustomKey = POWERUSERS,
array.
Using from [Settings], CustomKeysSysprep: CustomKey = COMPUTERNAME,
current value = %OSDNEWMACHINENAME%
Using from [Settings], CustomKeysSysprep: CustomKey = TIMEZONE, current
value = 250
Using from [Settings], CustomKeysSysprep: CustomKey = JOINDOMAIN,
current value = XXXX
Using from [Settings], CustomKeysSysprep: CustomKey = MACHINEOBJECTOU,
current value = OU=YYYY Computers,DC=XXXX,DC=aa,DC=bbb,DC=au
Using from [Settings], OSDVariableKeys: CustomKey = OSDINSTALLSILENT,
current value = 1
Using from [Settings], OSDVariableKeys: CustomKey = OSDINSTALLPACKAGE,
current value =
Using from [Settings], OSDVariableKeys: CustomKey = OSDINSTALLPROGRAM,
current value =
Using from [Settings], OSDVariableKeys: CustomKey = OSDNEWMACHINENAME,
current value =
----------------------- End Initialization -----------------------
Already connected to server XXXXSMS00 as it is the current distribution
point.
ZTI script starting processing for POSTINSTALL phase.
Successfully located Sysprep.inf at C:\Sysprep\sysprep.inf
Checking to see if drivers need to be copied.
No driver path was specified via DriverPath key - no copying will be
done.
0 driver directories copied successfully.
------ Updating Sysprep.inf ------
Updated C:\Sysprep\sysprep.inf section [UserData] with
COMPUTERNAME=%OSDNEWMACHINENAME% (value was *)
Updated C:\Sysprep\sysprep.inf section [GuiUnattended] with
TIMEZONE=250 (value was 250)
Updated C:\Sysprep\sysprep.inf section [Identification] with
JOINDOMAIN=XXXX (value was XXXX)
Updated C:\Sysprep\sysprep.inf section [Identification] with
MACHINEOBJECTOU=OU=YYYY Computers,DC=XXXX,DC=aa,DC=bbb,DC=au (value was
"OU=YYYY Computers,DC=XXXX,DC=aa,DC=bbb,DC=au")
Original C:\Sysprep\sysprep.inf section [Unattended]
OemPnPDriversPath="Drivers\AUD;Drivers\NIC;Drivers\VID;Drivers\CHP"
Checking "C:\Drivers" for driver directories to add
Found new driver path: \Drivers\AUD
Found new driver path: \Drivers\CHP
Found new driver path: \Drivers\NIC
Found new driver path: \Drivers\VID
Updated C:\Sysprep\sysprep.inf section [Unattended] with
OemPnPDriversPath="Drivers\AUD;Drivers\NIC;Drivers\VID;Drivers\CHP;\Drivers\AUD;\Drivers\CHP;\Drivers\NIC;\Drivers\VID"
------ Updating DevicePath Registry Value ------
Successfully loaded new OS software registry hive using
"C:\WINDOWS\system32\config\software".
Original
DevicePath=%SystemRoot%\inf;%SystemDrive%\Drivers\NIC;%SystemDrive%\Drivers\VID;%SystemDrive%\Drivers\CHP;%SystemDrive%\Drivers\AUD
Checking "C:\Drivers" for driver directories to add
Updated
DevicePath=%SystemRoot%\inf;%SystemDrive%\Drivers\NIC;%SystemDrive%\Drivers\VID;%SystemDrive%\Drivers\CHP;%SystemDrive%\Drivers\AUD
Updating OSD Shared memory with UDSHARE=\\XXXXSMS00\MigData
Updating OSD Shared memory with UDDIR=%OSDCOMPUTERNAME%
Updating OSD Shared memory with UDPROFILES=*\*
Updating OSD Shared memory with SLSHARE=\\XXXXSMS00\BDDLogs
Updating OSD Shared memory with OSINSTALL=Y
Updating OSD Shared memory with
ADMINISTRATORS=XXXX\DLG-CISSOELOCALADMIN
Not updating OSD Shared memory with blank value for DRIVERPATH
Updating OSD Shared memory with COMPUTERNAME=%OSDNEWMACHINENAME%
Updating OSD Shared memory with TIMEZONE=250
Updating OSD Shared memory with JOINDOMAIN=XXXX
Updating OSD Shared memory with MACHINEOBJECTOU=OU=YYYY
Computers,DC=XXXX,DC=aa,DC=bbb,DC=au
Updating OSD Shared memory with OSDINSTALLSILENT=1
Not updating OSD Shared memory with blank value for OSDINSTALLPACKAGE
Not updating OSD Shared memory with blank value for OSDINSTALLPROGRAM
Not updating OSD Shared memory with blank value for OSDNEWMACHINENAME
Updating OSD Shared memory with ZTISettings=1

ZTI POSTINSTALL processing completed successfully.
Copying local logfile
(C:\MININT\SMSOSD\OSDLOGS\zerotouchinstallation.log) to
\\XXXXSMS00\BDDLogs\.log

**********************************************************************************************


[Settings]
Priority= Model, DefaultGateway, SQL, Default
CustomKeysUserData=UDShare,UDDir,UDProfiles,SLShare,OSInstall,Packages(*),Administrator,DriverPath,PowerUsers(*)
CustomKeysSysprep=ComputerName,TimeZone,JoinDomain,MachineObjectOU
OSDVariableKeys=OSDINSTALLSILENT,OSDINSTALLPACKAGE,OSDINSTALLPROGRAM,OSDNEWMACHINENAME
ScanStateArgs=/i:miguser.inf /i:migapp.inf /i:migsys.inf
/i:sysfiles.inf /i:updateuser.inf /i:userdata.inf /v:7 /x /s /f /o /c
LoadStateArgs=/v:7 /c

[Default]
UDShare=\\XXXXSMS00\MigData
SLShare=\\XXXXSMS00\BDDLogs
Administrator=XXXX\DLG-CISSOELOCALADMIN
UDProfiles=*\*
OSDINSTALLSILENT=1
TimeZone=250
JoinDomain=XXXX
MachineObjectOU= OU=XXXX Computers,DC=XXXX,DC=sa,DC=gov,DC=au
UDDir=%OSDCOMPUTERNAME%
OSInstall=Y
ComputerName=%OSDNEWMACHINENAME%

[DefaultGateway]
10.35.64.1=SiteA

[SiteA]
UDShare=\\XXXXSMS00\MigData
SLShare=\\XXXXSMS00\BDDLogs
SQLDefault=BDDDB
Administrator=XXXX\DLG-CISSOELOCALADMIN

[Evo N1000c]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\N1000c
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[HP Compaq dc7100 SFF]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\DC7100SFF
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[Evo D510 SFF]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\d510sff
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[HP Compaq dc7600 Small Form Factor]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\dc7600SFF
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[8172A1M]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\IBM\8172A1M
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[8172KMA]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\IBM\8172KMA
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[HP d530 SFF]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\d530SFF
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[HP Compaq nc8000]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\nc8000
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[HP Compaq nc8230]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\nc8230
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[OptiPlex GX150]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\Dell\GX150
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[633966A]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\IBM\633966A
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[HP d530 CMT]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\d530CMT
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[Evo D510 CMT]
DriverPath=\\XXXXsms00\Drivers\XPProSP2\HP-Compaq\d510CMT
;OSDINSTALLPACKAGE=
;OSDINSTALLPROGRAM=

[BDDDB]
SQLServer=XXXXSMS00
Database=BDDAdminDB
Table=BDDAdminCore
Parameters=MacAddress
StoredProcedure=BDDAdminCore
SQLShare=BDDLogs

[SysprepInfMapping]
ComputerName=UserData
TimeZone=GuiUnattended
JoinDomain=Identification
MachineObjectOU=Identification
 
G

Guest

Just found a tid bit in the Deployment Feature Team guide saying to
include the SQLOLEDB.RLL and DBNMPNTW.DLL in the base OSDWinPE.wim. The
guild is very light on detail here. It doesn't say where to put the
file within the ISO? I'm gussing i386\system32. Looking at the Refresh
ZTI logs, these files are copied to MININT, but under bare metal no
such writeable place exists.

I'm going to rebuild the base WinPE and try. Will update with results.

Rob
 
J

Johan Arwidmark

SQLOLEDB.RLL goes to PROGRAM FILES\COMMON FILES\SYSTEM\OLE DB

DBNMPNTW.DLL to \I386\SYSTEM32


regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment
 
G

Guest

Cheers,

Turns out the SQLOLEDB.RLL was already inplace. Just the DBNMPNTW.DLL
was missing.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top