After the machine is built during the last stage of the the build when it is installing packages one by one that it resolves form sql all of a sudden it will lose the ability to connect to SQL randomly, it will then skip all remain packages but definately still has network connectivity as it copies the TS log files up to a server share before exiting. If I change the order of packages it still happens randomly on a different package so it's not an app that is causing the issue. but when i say randomly it will always fail on the same random package (yes deleted the minint folder and formatted). If I move the packages around and it will always fail on a completely different package. This is happening on laptops and desktops of various make models with various different packages assigned to them. anyone seen this? once it happens it will do the below on all the remain 20ish packages in a matter of 2 seconds post the log up to my server and exit. About to issue SQL statement: SELECT * FROM v_Program WHERE PACKAGEID = 'GST0048F' AND PROGRAMNAME = 'Toshiba_TouchPad_OnOff_Utility_2.5.1' ERROR - Opening Record Set (Error Number = -2147467259) (Error Description: Connection failure). ADO error: Connection failure (Error #-2147467259; Source: Microsoft OLE DB Provider for SQL Server; SQL State: 08S01; NativeError: 0)

Hi, Is it a local SQL database or a remote database for your SCCM site server? Did you properly configure the network access account? could you please check SQL error on your SQL server to see if some connection error is logged.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

As this thread has been quiet for a while we will be changing the issue type to ‘General Discussion’. If you wish to return to this question you can go ahead and change the type back to ‘Question’. Then you can edit your initial post and change the radio button at the top of the post editor window. If the issue has been resolved, we’d love to hear your solution. By sharing your experience you can help other community members facing similar problems. Thanks!Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.