Would an overly large drivers.xml break it ? My XML is about 2 megs John Bain NHQ - Solutions and Information Management | AC - Direction générale des solutions et de la gestion de l'information Citizenship and Immigration Canada | Citoyenneté et Immigration Canada 365 Laurier Avenue West Ottawa ON K1A 1L1 | 365, avenue Laurier Ouest Ottawa ON K1A 1L1 [email protected]<mailto:[email protected]> Telephone | Téléphone 613-954-2536 Facsimile | Télécopieur 613-952-7171 Government of Canada | Gouvernement du Canada From: [email protected] [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: July 29, 2014 12:57 PM To: [email protected] Subject: RE: [MDT-OSD] Weird MDT error while importing drivers
>From the error, it seems unlikely that this is related to a corrupt XML file. >It seems more likely that it's a problem with parsing the INF file for the >driver in question. But if it works on one deployment share and not on >another, then there is something else going on since a bad INF would always >fail. The usual suspects: * Overly-aggressive antivirus software. * Different versions of the OS (where it works vs. where it doesn't). Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bain.John Sent: Tuesday, July 29, 2014 9:42 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Weird MDT error while importing drivers It seems to work with a new deployment, is there a way to repair a corrupted drivers.xml ? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Keith Garner (Hotmail) Sent: July 29, 2014 12:40 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Weird MDT error while importing drivers Either... Your driver is bad, and MDT can't parse it. Or... Your MDT control\drivers.xml is corrupted, and MDT can't write to it. Try importing this driver to a *new* deployment share, to see if it's a problem with the driver, then you may need to rebuilt the drivers by copying back and forth between deployment shares. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bain.John Sent: Tuesday, July 29, 2014 8:47 AM To: '[email protected]' Subject: [MDT-OSD] Weird MDT error while importing drivers Having trouble import drivers into an older MDT deployment... getting this error message System.Management.Automation.CmdletInvocationException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.ThrowHelper.ThrowArgumentOutOfRangeException() at System.Collections.Generic.List`1.get_Item(Int32 index) at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile) at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath) at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath) at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath) at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath) at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath) at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath) at Microsoft.BDD.PSSnapIn.ImportDriver.ProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord() --- End of inner exception stack trace --- at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper() at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc() The whole message log can be seen here http://pastebin.ca/2826929 John
