|
| Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page. | |
| | Author | Messages | |
MattGoldencrown
Posts:2
 | | 01/31/2008 2:03 PM |
| Hi All - Doozy of a puzzle I've run into that doesn't seem to have an easy resolution. We're running BDD 2007, fresh vanilla install. WDS is installed and serving out the WIM created. We're able to run through the setup wizard, and are able to access the distrubition share on the lab deployment point. The problem lies in as soon as the initial wizard completes, and as far as I can tell the task sequencer is attempted to be accessed, an error occurs stating "Non-zero return code executing command "X:\Deploy\Tools\X86\TsmBootstrap.exe" /env:SAStart, rc = -2147467259". Looking this up in SMS Trace via hex translation turns up an "Unspecified Windows Error". We've tried this on multiple hardware platforms, and both with and without capturing an image. We've currently got the network access credentials entered and functioning for the lab deployment point, as we can access the z: drive from within WinPE. I've attached the log file generated during the build and would appreciate any suggestions on how we can get this implementation working. Thanks, Matt |
 Attachment: MININT-2BV803V.log
| | |
| Mike Dzikowski
Deployment Forum MVP
Posts:122
| | 02/01/2008 4:30 PM |
| Hi Matt-
Have you tried formatting that drive. Then trying to re-deploy that image?
Mike | |
Mike Dzikowski, MCP | |
| DiogoSousa
Posts:13
| | 02/04/2008 2:59 AM |
| Hi there, and greetings from Portugal!
Have you add WindowsMedia11-KB929399-v2-x86 hotfix to your deployment?
I've add some issues we that, explained at my blog (http://frontslash.wordpress.com).
I haven't found a good workaround for this yet... | |
Systems Analyst (Portugal) - http://frontslash.wordpress.com | |
| MattGoldencrown
Posts:2
| | 02/05/2008 12:58 PM |
| To answer the suggestions above, the client capture machine had been formatted and started off from scratch with the same results, and this build had no applications being installed or OS patches being applied (just a straight XP build/capture for reference). The issue was resolved in this case by actually removing BDD 2007 (and WDS, but I don't believe that was causing the problem) and installing Deployment. Once Deployment was installed, the task sequencer started up without any problem and the capture went through. My only thought is that the Tsmbootstrap was corrupt, or one of the resulting bin's called by the bootstrapper was bad. Thanks for the suggestions! | | | |
| Marshall
Posts:4
| | 02/08/2008 10:17 AM |
| We encountered three such TsmBootstrap.exe errors (-2147467259) this week that we're still trying to diagnose. Any suggestions would be appreciated as to how to intercept these pre-crash.
We're pretty convinced one was caused, at least in part, by the attending technician having rebooted the LiteTouch CD into WinPE where this was accompanied by the ZTITatoo error below.
ERROR - ZTITatoo state restore task should be running in the full OS, aborting. Two others failed when the PC was not defined in the Make & Model database, which reported in LiteTouch.log but the word ERROR was glaringly omitted (bad form Mr. Gates).
LTI deployment failed Property RetVal is now = -2147467259 This last one also complained about the SLShare value and missing TSCore.dll in the same session, not even a "failure" message to search for here. Unable to copy log to the network as no SLShare value was specified. TSCore.dll not found, not unregistering.
| | | |
| Mike Dzikowski
Deployment Forum MVP
Posts:122
| | 02/08/2008 1:40 PM |
| Marshal-
For this
This last one also complained about the SLShare value and missing TSCore.dll in the same session, not even a "failure" message to search for here. Unable to copy log to the network as no SLShare value was specified.
You'll have to create a SQL Share and add it to your CS.ini for your database entries. For instance:
[CPackages]
SQLServer=mivw106
Instance=sqlexpress
Database=DeploymentDB
Netlib=DBNMPNTW
Table=ComputerPackages
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
Order=Sequence
SQLShare=\\YOURSERVER\SQLShare$
[CApps]
SQLServer=mivw106
Instance=sqlexpress
Database=DeploymentDB
Netlib=DBNMPNTW
Table=ComputerApplications
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
Order=Sequence
SQLShare=\\YOURSERVER\SQLShare$
[CAdmins]
SQLServer=mivw106
Instance=sqlexpress
Database=DeploymentDB
Netlib=DBNMPNTW
Table=ComputerAdministrators
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
SQLShare=\\YOURSERVER\SQLShare$
Mike Dzikowski
| |
Mike Dzikowski, MCP | |
| Marshall
Posts:4
| | 02/24/2008 6:09 PM |
| Thanks for the clarification, it had not occurred to me that the SLShare message was referring to the SQL name.
Meanwhile for those computer models not included in our Make & Model database, we've now modified the USEREXIT.VBS script to "translate" the various BIOS signatures in our inventory. This populates the MODELALIAS variable based on the list of known part numbers, which is passed to the [MMAPPLICATIONS] parameters.
There are still a variety of nonstandard systems though, and these will probably be taken out of service by just halting the USEREXIT.VBS script, where the model is not recognized. | | | |
|
| | You are not authorized to post a reply. |
|
| |
ActiveForums 3.7 | |
|  | These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums: - We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
- Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
- Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
- Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
- Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
- Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.
We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum. |
| |
| |
|