Powershell script returns the exception "Cannot index into a null array"

Hi,
$userName = $item["Editor"];
$DocID = $item["_dlc_DocId"];
Above lines on execution returns the below error.
Cannot index into a null array.
At C:\GetAllInvoices.PS1:23 char:26
+           $userName = $item[ <<<< "Editor"];
    + CategoryInfo          : InvalidOperation: (Editor:String) [], RuntimeExc
   eption
    + FullyQualifiedErrorId : NullArray
Cannot index into a null array.
At C:\GetAllInvoices.PS1:24 char:30
+               $DocID = $item[ <<<< "_dlc_DocId"];
    + CategoryInfo          : InvalidOperation: (_dlc_DocId:String) [], Runtim
   eException
    + FullyQualifiedErrorId : NullArray
Any solution ?
Thanks in advance,
Dhileep

The error indicates $item is either not an array or an empty array.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Similar Messages

PowerShell: Cannot index into a null array

I am trying to put together a script that will upload documents into a document library. Here is what my script looks like currently...
$fileStream = ([System.IO.FileInfo] (Get-Item $file.FullName)).OpenRead()
$FileName = $File.Name
$NewName = [IO.Path]::GetFileNameWithoutExtension($FileName)
$FileNameArray = $NewName.split("_")
$check = $FileNameArray.Length
Write-Host "My Array:" $FileNameArray
Write-Host "Array Length:" $check
#Add file
$folder = $web.getfolder($docLibrary.rootFolder.URL)
write-host "Copying file " $file.Name " to " $folder.ServerRelativeUrl "..."
$spFile = $folder.Files.Add($folder.Url + "/" + $file.Name, [System.IO.Stream]$fileStream, $true)
$spItem = $spFile.Item
#populate columns
$spItem["First Column"] = $FileNameArray[0].ToString()
$spItem["Second Column"] = $FileNameArray[1].ToString()
$spItem.Update()
$fileStream.Close();
Currently when my script tries to update the columns with the elements from the array, I am getting this error message
Cannot index into a null array.
At C:\powershellscripts\Upload-FilesIntoSharePoint.ps1:164 char:6
+ $spItem["First Column"] = $FileNameArray[0].ToString()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : NullArray
...earlier in the script, I placed checks to see what my array is like, and it hold data. When I ran it, I had 2 elements in my array, those values where printed to the console. However, the script stalls when am trying to get the values into the respective
columns. Does anyone have an idea why this is happening? Thanks.

Hi,
first of all ensure that NewName has at least one underscore and then debug the code to see the value of $FileNameArray[0].
Regards.
If a post answers your question, please click Mark As Answer on that post and
Vote as Helpful

Cannot index into a null array

Hi there,
I am getting Cannot index into a null array error. I run the script below.
Function check-even ($num) {[bool]!($num%2)}
foreach ($file in (Get-ChildItem -Path c:\Users\rsimmers\desktop\*.ini)) {
    "Processing file {0}" -f $file
    $newfilename = $file.fullname -replace ".ini", ".txt"
    $newContent = foreach ($line in (Get-Content $file.fullname)){
        $printer = $line -match '\| (.*?)"'
        $printerName = $Matches[1]
        $printerNum = $printerName.Split("-")[2]
        if((check-even $printerNum) -eq $true) {
            #even
            $line.Replace('Host="ACFILE01"','Host="VJJJRT02"').Replace('Host="effile01"','Host="VJJJRT02"')
        else {
            #odd
            $line.Replace('Host="ACFILE01"','Host="VSHHPRT01"').Replace('Host="ACFILE01"','Host="VSHHPRT01"')
$newContent
$newContent | Out-File $newfilename
Processing file \\vfs04\Users$\kaendm\Desktop\Test00E8E627F9C.ini
Cannot index into a null array.
At C:\Powershell\TReplaceIniValues.ps1:12 char:9
+ $printerName = $Matches[1]
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : NullArray
You cannot call a method on a null-valued expression.
At C:\Powershell\TReplaceIniValues.ps1:13 char:9
+ $printerNum = $printerName.Split("-")[2]
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

Hi
In the script above, what is the best way to create an statement. I also want replace some values which do not have to pass equal to or add test.
***For the following Host names (ZFILE01, WPRINT01) replace the values regardless.
.Replace('Host="ZFILE01"','Host="BKBprt01"').Replace('Host="WPRINT01"','Host="BHHprt01"')
*** For the rest of the Host names perform the (Odd/Even check)
if((check-even
$printerNum)-eq
$true){
#even
$content[$i]=$content[$i].Replace('Host="ACFILE01"','Host="VJJJRT02"').Replace('Host="effile01"','Host="VJJJRT02"')
else{
#odd
$content[$i]=$content[$i].Replace('Host="ACFILE01"','Host="VSHHPRT01"').Replace('Host="ACFILE01"','Host="VSHHPRT01"')

PowerShell command returned an exception. Unexpected token 's' in expression or statement

Hi All,
I am trying to Creating a VM based on a Template in VMM through Orchestrator Runbook using below URL;
http://blogs.catapultsystems.com/lrayl/archive/2013/07/03/orchestrator-system-center-integrations-part-3-creating-a-vm-based-on-a-template-in-vmm.aspx
Runbook:
But at the Create VM from Template activity runbook will failed:
Throwing below error in while running runbook in Error Summary text:
PowerShell command returned an exception. Unexpected token 's' in expression or statement.
Exception: InvalidOperationException
Target site: PSRunspaceInvoker.HandleInvokeException
Stack trace:
at Microsoft.SystemCenter.Orchestrator.Integration.PowerShellConnector.PSRunspaceInvoker.HandleInvokeException(Exception ex, ILogger logger)
at Microsoft.SystemCenter.Orchestrator.Integration.PowerShellConnector.PSRunspaceInvoker.Invoke(RunspaceInvoke runspace, String script, ILogger logger)
at Microsoft.SystemCenter.Orchestrator.Integration.PowerShellConnector.PSScriptRunner.Execute(String script)
at Microsoft.SystemCenter.Orchestrator.Integration.VMM2012Domain.VM.CloneFromTemplate(String vmmServer, ParameterList inputParameters)
at Microsoft.SystemCenter.Orchestrator.Integration.VMM2012QIK.VM.CloneFromTemplate.DoExecute(IActivityRequest request, ILogger logger)
at Microsoft.SystemCenter.Orchestrator.Integration.VMM2012QIK.ActivityBase`2.Execute(IActivityRequest request, IActivityResponse response)
Both Orchestrator & SCVMM powershell are set on Unrestricted powershell.
Kindly suggest any solution or work around for resolution.
Thanks Rahul$

This may be a bit late and perhaps not even relevant but I came across this post when trying to solve an issue I had with a powershell script in Orchestrator. Maybe it will help you, or maybe it will help someone else.
I was trying to create a connector between SCOM and our ticketing system. I wanted to export alert descriptions and in the process of testing I came across an alert description that had multiple lines and all kinds of crazy formatting. When I tried to assign
the Published Data to a varialbe in my powershell script i would get an error "Unexpected token [a partial alert description] in expression or statement.". After looking at the actual alert description data and seeing that i was only getting some of it
and not all of it it dawned on me that i somehow needed to escape out of all the crazy quoting, carriage returns, and special characters. to do that i assigned the Published Data to a variable in my powershell script as follows:
$Description = @"
{Description from "Get Alert"}
Apparently the @" "@ is called a here-string. Somewhat interesting. Hope it helps you or someone else!

SQL Server upgradation Issue : 2012 to 2014. A job step received an error at line 1 in a PowerShell script. The corresponding line is 'set-executionpolicy RemoteSigned -scope process -Force'. Correct the script and reschedule the job.

Message
Executed as user: CORPTST\XXXXX. A job step received an error at line 1 in a PowerShell script. The corresponding line is 'set-executionpolicy RemoteSigned -scope process -Force'. Correct the script and reschedule the job. The error information returned
by PowerShell is: 'Security error. '. Process Exit Code -1. The step failed.
I receive this error during the sql server job 'syspolicy_purge_history' execution when sql server got upgraded form SQL Server 2008 to 2014.

Hi Vishnu,
According to the error message, it also occurs in SQL Server 2012. Here is a feedback about the error in the link below.
https://connect.microsoft.com/SQLServer/feedback/details/754063/sql-server-2012-syspolicy-purge-history-job-step-3-fails-with-security-error
To resolve this issue, please change the value of the following registry key from ‘RemoteSigned’ to ‘Unrestricted’. For more details, you can review this similar
blog.
HKLM\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps120\ExecutionPolicy
Thanks,
Lydia Zhang

Can we execute a Powershell script from the Javascript?

Hi,
I have a certain requirement to add a Custom ribbon button in document library and there was a powershell script to be run for the selected item in the library.
I have struck with executing a Powershell script from the javascript function.
Can anyone please suggest me if this was achievable
Thanks, Swaroop Vuppala

Hi Swaroop,
To execute server side code in a custom ribbon button script, using application page is a common way to do this, besides, you can also use a page dialog, which is similar with application page but display as model dialog, another way is javascript
_dopostback and delegate control, the following article contains detailed information about this, please refer to it for more information:
Invoke server side code on SharePoint ribbon click:
http://sharepointnadeem.blogspot.in/2012/07/invoke-server-side-code-on-sharepoint.html
Thanks,
Qiao Wei
TechNet Community Support

Can anyone help with a powershell script using the search-adaccount cmdlet to filter out accounts that have been created in the last 90 days?

Hi,
I have the following script that is supposed to search AD for all user accounts that haven't logged into the domain in more than 90 days. I first did not have the where-object clause because I didn't realize the search-adaccount would provide results
back of users that have never logged in, but were created less than 90 days ago. So I tried to incorporate the logic to not include user accounts that were created in the last 90 days.
#requires -version 4
#This script creates a file of accounts that have not been logged into in the past 90 days, excluding accounts that have been created within the past 90 days since the -AccountInactive option does not factor for the whenCreated property of an AD object
$DateThreshold = ((Get-Date).AddDays(-90))
$ReportDate = Get-Date -Format yyyy-MM-dd
#Create a folder according to the current date to be used for storing the report
New-Item -Path ".\$ReportDate" -ItemType Directory
$InactiveUsers = Search-ADAccount -UsersOnly -AccountInactive -TimeSpan "90" -SearchBase "OU=XXXX,DC=XXXX,DC=XXXX,DC=XXXX" | Where-Object {$_.whenCreated -gt $DateThreshold} | Export-Csv ".\$ReportDate\Inactive90_$ReportDate.csv"
However, I can't ever get the whenCreated field to populate with data. What gives?

Hi,
Search-ADAccount doesn't return a whenCreated property. If you want that, you'll need to use Get-ADUser as well. Here's a basic example you can build from:
$dateThreshold = (Get-Date).AddDays(-90)
Search-ADAccount -UsersOnly -SearchBase 'OU=Users,DC=domain,DC=com' -AccountDisabled | ForEach {
$whenCreated = (Get-ADUser -Identity $_.SamAccountName -Properties whenCreated).whenCreated
If ($whenCreated -gt $dateThreshold) {
$_
Don't retire TechNet! -
(Don't give up yet - 12,950+ strong and growing)

Running a function from a powershell script from the command line

Rather than creating several scripts each with one function, I have one script with has several functions.... I would like to call the script and select the function i want to use from the command line.
so far, if i change directory to that of the script i can call the function by doing this:
cd c:\myscripts
. .\mytestscript.ps1; myfunction
this works fine.... i have also tried, what I would like to achieve is calling it like this
c:\myscripts\mytestscript.ps1; myfunction
however, i am trying to run this as part of an MDT task sequence, my command line looks like this and using the ; myfunction at the end doesn't work.
powershell.exe -ExecutionPolicy Bypass %SCRIPTROOT%\CustomScripts\mytestscript.ps1; myfunction
how can i adapt my command line so that it will successfully call the function within my script?
thanks
Steve

Rename the file from ps1 to psm1 and create a powershell module that contain multiple functions. A module will autoload like the built-in modules.
Placement of the psm1 file is important for Powershell to find and autoload it.
The file name and folder name must be the same, for example MyModule.psm1 should be in the folder:
user\documents\windowspowershell\modules\mymodule
Windows PowerShell Modules
http://msdn.microsoft.com/en-us/library/dd878324(v=vs.85).aspx
PS C:\> get-childItem env:PSModulePath
Name Value
PSModulePath C:\Users\User\Documents\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules\

PowerShell Script Get the User's Active Directory Fully Qualified Login Name for Specific Locked Out Accounts

I have a script which displays locked out accounts. It works great.
I'd like to display the fully qualified Active Directory Login Name instead of the LastName, First Name:
Example: Davis, Susan
Want instead: Domain\Susan.Davis
I'd also like to include an additional filter to look for only Domain\Susan.Davis OR Domain\Robin.Givens
Here is my script:
$objDomain = New-Object System.DirectoryServices.DirectoryEntry
$objSearcher = New-Object System.DirectoryServices.DirectorySearcher
$objSearcher.SearchRoot = $objDomain
$objSearcher.PageSize = 1000
$objSearcher.Filter = "(&(objectClass=User)(lockoutTime>=1))"
$colProplist = "name","samaccountname"
foreach ($i in $colPropList){$objSearcher.PropertiesToLoad.Add($i) | out-null}
$colResults = $objSearcher.FindAll()
foreach ($objResult in $colResults) {
$domainname = $objDomain.name
$samaccountname = $objResult.Properties.samaccountname
$user = [ADSI]"WinNT://$domainname/$samaccountname"
$ADS_UF_LOCKOUT = 0x00000010
if(($user.UserFlags.Value -band $ADS_UF_LOCKOUT) -eq $ADS_UF_LOCKOUT) {
$objResult.Properties.name
John
John

Sorry, I should have mentioned that the cmdlets I'm using are part of the Active Directory module. You'll need to install the RSAT (Win7+) to use them.
If you'd rather stick with your DirectorySearcher methods instead of moving to the AD module, you can adjust your output by using something like this instead:
if(($user.UserFlags.Value -band $ADS_UF_LOCKOUT) -eq $ADS_UF_LOCKOUT) {
"$domainname\$($objResult.Properties.samaccountname)"
$domainname might not be what you're expecting, just FYI.
As for filtering, you can add to the if statement and check for your known usernames only.
Don't retire TechNet! -
(Don't give up yet - 12,700+ strong and growing)

Get the daily incremental search crawl information using PowerShell script

Dear Friends ,
I want to get the daily incremental search crawl information using PowerShell script . I need this information into CSV or txt format . Can you please help me with this.
valmiki

Hi
I have got the below script which worked .
## SharePoint Reference
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Administration")
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server.Search.Administration")
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server.Search")
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server")
function global:Get-CrawlHistory($url)
trap [Exception] {
write-error $("ERROR: " + $_.Exception.GetType().FullName);
  write-error $("ERROR: " + $_.Exception.Message);
  continue;
$s =
new-Object Microsoft.SharePoint.SPSite($url);
$c = [Microsoft.Office.Server.Search.Administration.SearchContext]::GetContext($s);
$h =
new-Object Microsoft.Office.Server.Search.Administration.CrawlHistory($c);
Write-OutPut $h.GetCrawlHistory();
$s.Dispose();
Get-CrawlHistory
-url  http://your_site_url/
|
Export-CsvF:\temp\search.csv
valmiki

Does anyone have a PowerShell script which change the paper source on a Canon Image Runner Advance?

I came across this Powershell script on the web, which does a good job of printing out PDFs:
Start-Process -FilePath "C:\Users\Test\Documents\Listing.pdf” –Verb Print -PassThru | %{sleep 10;$_} | kill
Start-Process -FilePath “C:\Users\Test\Documents\Scan0001.pdf” –Verb Print -PassThru | %{sleep 10;$_} | kill
Start-Process -FilePath “C:\Users\Test\Documents\Scan0004.pdf” –Verb Print -PassThru | %{sleep 10;$_} | kill
See: http://gregcaporale.wordpress.com/2012/01/18/powershell-to-print-files-automatically/
What I want to know is, does someone know how to write a Powershell script so that before printing out each PDF, a tab will be pulled from a separate paper source tray. I need the Powershell script to
1. Set the paper source to tray 4 where the tabs are.
2. Print a one page PDF which just reads "Tab 1" or whatever, on the tab itself
3. Set the paper source to ray 1 where letter sized paper is.
4. Print a PDF of the document to go behind tab 1.
. . . and then repeat.
I am working with a Canon Image Runner Advance copier/printer into which tabs can be loaded. It includes an insert sheets setting in the properties, which allows a user to specify the pages where a tab or slip sheet should go. But I don't want to deal with creating a very large PDF, and then identifying all of the pages where an insert should occur.

Here is the powershell code for adding ips to relayiplist..hope this helps.
this code will take the ips of the host machine and add it to the relayiplist...works for me...
$Networks = Get-WmiObject Win32_NetworkAdapterConfiguration -ComputerName localhost | ? {$_.IPEnabled}
$ipblock= @(24,0,0,128,
32,0,0,128,
60,0,0,128,
68,0,0,128,
1,0,0,0,
76,0,0,0,
0,0,0,0,
0,0,0,0,
1,0,0,0,
0,0,0,0,
2,0,0,0,
1,0,0,0,4,0,0,0,0,0,0,0,76,0,0,128,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,255,255,255,255)
$ipList = @()
$octet = @()
foreach ($Network in $Networks)
    $ipList = $Network.IpAddress[0]
        $octet += $ipList.Split(".")
        $ipblock[36] +=1
        $ipblock[44] +=1;
$smtpserversetting = get-wmiobject -namespace root\MicrosoftIISv2 -computername localhost -Query "Select * from IIsSmtpServerSetting"
$ipblock += $octet
$smtpserversetting.RelayIpList = $ipblock
$smtpserversetting.put()
kautilya

Capture error code returned by VB script from the OIM Remote Manager

Hi All,
I am trying to provision to Exchange using powershell and OIM remote Manager.
RM is installed in the Exchange server and a VB script is called by the RM to perform the necessary provisioning operations.
Certain error codes are configured in VB script according to the script execution.
How can I get the return codes back to the RM and then to OIM adpater, so that I can publish appropriate error messages by writing them in the Adapter responses.
Below is my current code, but it does not capture return codes.
Can the variable 'i' get the return codes fron the VB script?
if (fScriptFile.exists())
String sCmd = scriptPath + " " + sUPN;
log.debug("Firing Powershell command:" + sCmd);
Process localProcess = localRuntime.exec("cscript.exe " + sCmd);
log.debug("Script Executed ");
int i = localProcess.waitFor();
localProcess.getOutputStream().close();
log.debug("Process Exit Value " + i);
sResult = i == 0 ? "EXCHANGE.REMOTE_SCRIPT_RUN_FAILURE" : "EXCHANGE.REMOTE_SCRIPT_RUN_SUCCESS";
Please help..
Thanks and Regards.

Your VB script must be calling a powershell script.Check if powershell script returns any error message to your vbscript.I

Powershell Script to change the target destination on a shortcut file.

Hi All,
I am in a middle of a new file server implementation and have come across a problem where the items on the old file server has been archived and moved to another server and in place a shortcut is left at the original location. The current target of those
shortcut is going to be changed and thus I need to change the Target destination on those various shortcuts files. I am new to powershell and will really appreciate if someone can assist me with a powershell script for the below steps:
To find all shortcut files (Excel, word, powerpoint and other types) whose current target destination is \\abcserver\z\abcpath
Change the Target destination to \\xyzserver\z\abcpath on the shortcut file and apply the change.
Effectively only change shortcut files whose current target begins with "\\abcserver\" and change to "\\xyzserver\"
Search for the next shortcut and continue changing it.
Hope the above makes sense and appreciate the assistance.
Thanks!

Did you look?
https://www.google.com/?gws_rd=ssl#newwindow=1&q=powershell+change+shortcut+path
¯\_(ツ)_/¯

PowerShell - scripting - skip Encrypted\CLR Stored Procedures

Hi all,
Forgot where I got the code below from but, how would I skip Encrypted\CLR procedures because, I get error below...
Message
Executed as user: Loginname A job step received an error at line 81 in a PowerShell script. The corresponding line is '
$MyScripter.Script($proc)|out-null'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'Exception calling "Script" with "1" argument(s): "The StoredProcedure '[dbo].[myrpocname]'
cannot be scripted as its data is not accessible." '. Process Exit Code -1. The step failed.
#STORED PROCEDURES
if($procs -ne $null)
foreach ($proc in $procs)
#Assuming that all non-system stored procs have proper naming convention and don''t use prefixes like "sp_"
if ( $proc.Name.IndexOf("sp_") -eq -1 -and $proc.Name.IndexOf("xp_") -eq -1 -and $proc.Name.IndexOf("dt_") -eq -1)
$fileName = $proc.name
"Scripting SP $fileName"
$scriptfile = "$rootDrive\DatabaseScripts\$sqlDatabaseName\$strDate\StoredProcedures\$filename.sql"
New-Item $rootDrive\DatabaseScripts -type directory -force | out-null
New-Item $rootDrive\DatabaseScripts\$sqlDatabaseName -type directory -force | out-null
New-Item $rootDrive\DatabaseScripts\$sqlDatabaseName\$strDate -type directory -force | out-null
New-Item $rootDrive\DatabaseScripts\$sqlDatabaseName\$strDate\StoredProcedures -type directory -force | out-null
# SetScriptOptions
$MyScripter.Options.FileName = $scriptfile
#AppendTofile has to be ''true'' in order that all the procs'' scripts will be appended at the end
$MyScripter.Options.AppendToFile = "true"
$MyScripter.Script($proc)|out-null
Thanks
gv
Sword

You can exclude encrypted stored procedure using $_.IsEncrypted member.
$storedProcs = $db.StoredProcedures | Where-object { $_.schema -eq $schema -and -not $_.IsSystemObject -and -not $_.IsEncrypted}
$server = "localhost"
$database = "PowerSQL"
$output_path = "F:\PowerSQL\"
$schema = "dbo"
$storedProcs_path = "$output_path\StoredProcedure\"
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMO") | out-null
$srv = New-Object "Microsoft.SqlServer.Management.SMO.Server" $server
$db = New-Object ("Microsoft.SqlServer.Management.SMO.Database")
$tbl = New-Object ("Microsoft.SqlServer.Management.SMO.Table")
$scripter = New-Object ("Microsoft.SqlServer.Management.SMO.Scripter") ($server)
# Get the database and table objects
$db = $srv.Databases[$database]
$storedProcs = $db.StoredProcedures | Where-object { $_.schema -eq $schema -and -not $_.IsSystemObject -and -not $_.IsEncrypted}
# Set scripter options to ensure only data is scripted
$scripter.Options.ScriptSchema = $true;
$scripter.Options.ScriptData = $false;
#Exclude GOs after every line
$scripter.Options.NoCommandTerminator = $false;
$scripter.Options.ToFileOnly = $true
$scripter.Options.AllowSystemObjects = $false
$scripter.Options.Permissions = $true
$scripter.Options.DriAllConstraints = $true
$scripter.Options.SchemaQualify = $true
$scripter.Options.AnsiFile = $true
$scripter.Options.EnforceScriptingOptions = $true
function CopyObjectsToFiles($objects, $outDir) {
if (-not (Test-Path $outDir)) {
[System.IO.Directory]::CreateDirectory($outDir)
foreach ($o in $objects) {
if ($o -ne $null) {
$schemaPrefix = ""
if ($o.Schema -ne $null -and $o.Schema -ne "") {
$schemaPrefix = $o.Schema + "."
$scripter.Options.FileName = $outDir + $schemaPrefix + $o.Name + ".sql"
Write-Host "Writing " $scripter.Options.FileName -ErrorAction silentlycontinue
$scripter.EnumScript($o)
# Output the scripts
CopyObjectsToFiles $storedProcs $storedProcs_path
Write-Host "Finished at" (Get-Date)
-Prashanth

MDT2012 - Deployment failed, the system cannot find the file specified

Hi everybody.
First, excuse me for my english, i think it's not the best thing I'm able to do, but now, I REALLY need help.
I encounter issues with my MDT 2012 Update 1 platform.
I have 5 systems to capture. All systems have 3 partitions (System, softwares, data). Capture is working fine for all parts.
In my Task Sequence, to deploy these images (C, D and E parts), I use a script after the "Install Operating System" which runs imagex to deploy the WIM images for D: and E:.
The script is the following :
"%DeployRoot%\Tools\x64\imagex" /apply "%DeployRoot%\Operating Systems\D_Drive\D_Drive.wim" 1 %DDrive%"
But, for some images, the task fails on the "D" drive deployement. The wizard shows the following error :
Litetouch deployment dailed, return code = -214767259 0x80004005
Failed to run the action: InstallD (ie : the script above)
The system cannot find the file specified. (Error: 00000002; Source: Windows)
The error is on my task which uses imagex to deploy my D and E WIM.
So I looked to see if the file's path was the good one.
And it is !!!
Wizard says that the file couldn't be find, but the file is existing, and in the good path.
For your information, there is no problem when I don't use multicast. Everything is working fine on unicast, not on multicast.
I even encounter this issue if I use my MDT server and my computers on the same switch.
Any help would be gratefull, my client gives me the week to resolve the issue.
Thanks

BDD.LOG
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Write all logging text to \\192.168.36.208\Logs$]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Already connected to server 192.168.36.208 as that is where this script is running from.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[OSDTargetDriveCache was determined earlier : V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDisk is now = V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Open Control File: OperatingSystems]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[------ Applying Windows image using ImageX.exe ------]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI applying image \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim using ImageX]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41023 sent: LTI applying image \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim using ImageX]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer to directory: C:\MININT\Operating Systems\Master 3 avec Sysprep]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[<Message containing password has been suppressed>]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1348)]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1348)]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 1348)]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Started.
]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 1348)]LOG]!><time="16:58:01.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 5 minutes (process ID 1348)]LOG]!><time="16:58:01.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Complete [0x0].]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer of "\\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim" to "C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim" completed successfully.]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Cleaning off old operating system]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Skipping V:\Drivers]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:" \\MININT-1H9O4H6\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Enabling 8dot3 name support on volume V:]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\192.168.36.208\MDT$\Tools\X64\imagex.exe" /apply "C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim" 1 V:]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread=""
file="LTIApply">
<![LOG[Command has been started (process ID 536)]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 0% ] Applying progress ]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 0% ] Applying progress ]LOG]!><time="17:00:49.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 1% ] Applying progress ]LOG]!><time="17:00:49.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 2% ] Applying progress ]LOG]!><time="17:00:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 3% ] Applying progress ]LOG]!><time="17:00:58.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 4% ] Applying progress: 5:28 mins remaining ]LOG]!><time="17:01:03.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 5% ] Applying progress: 5:33 mins remaining ]LOG]!><time="17:01:07.000+000"
<![LOG[ Console > [ 99% ] Applying progress: 3 secs remaining ]LOG]!><time="17:06:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 100% ] Applying progress ]LOG]!><time="17:06:50.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Successfully applied image.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Total elapsed time: 6 min 7 sec]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The image C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim was applied successfully.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 5625 sent: The image C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim was applied successfully.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\192.168.36.208\MDT$\Tools\X64\bootsect.exe" /nt60 V:]LOG]!><time="17:06:52.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1252)]LOG]!><time="17:06:52.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Target volumes will be updated with BOOTMGR compatible bootcode.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > V: (\\?\Volume{2ab15dec-99c9-19e3-baf6-94de80bab573})
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Successfully updated NTFS filesystem bootcode.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Bootcode was successfully updated on all targeted volumes.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Find the boot drive (if any) [True] [6.1.7601.18229] [False]]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\MININT-1H9O4H6\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDisk : \\MININT-1H9O4H6\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Ready to Prepare boot partition: V:]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: cscript.exe //nologo "\\192.168.36.208\MDT$\Scripts\ztiRunCommandHidden.wsf" ""\\192.168.36.208\MDT$\Tools\X64\BCDBoot.exe" V:\windows /l fr-fr /s V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread=""
file="ztiRunCommandHidden">
<![LOG[Write all logging text to \\192.168.36.208\Logs$]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Already connected to server 192.168.36.208 as that is where this script is running from.]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[About to run command: \\192.168.36.208\MDT$\Tools\X64\BCDBoot.exe V:\windows /l fr-fr /s V:]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Command has been started (process ID 1984)]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[ Console > Boot files successfully created.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Return code from command = 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Command has returned: 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Run Command: X:\WINDOWS\SYSTEM32\bcdedit.exe /Store "V:\boot\bcd" /timeout 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCD> The operation completed successfully.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Created scratch folder.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copy File: C:\MININT\unattend.xml to V:\Windows\Panther\Unattend.xml]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copied unattend.xml to V:\Windows\Panther for image apply.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: dism.exe /Image:V:\ /Apply-Unattend:V:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1516)]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Deployment Image Servicing and Management tool]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Image Version: 6.1.7600.16385]LOG]!><time="17:06:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > The operation completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTIApply processing completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41001 sent: LTIApply processing completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property RetVal is now = -2147467259]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Already connected to server 192.168.36.208]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[OSDTargetDriveCache was determined earlier : V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDisk is now = V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LiteTouch.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LiteTouch.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LTIApply.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LTIApply.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LTICopyScripts.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LTICopyScripts.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\PnpEnum.xml to \\192.168.36.208\Logs$\MININT-1H9O4H6\PnpEnum.xml]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\Wizard.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\Wizard.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIBDE.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIBDE.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIConfigure.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIConfigure.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIDiskpart.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIDiskpart.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIDrivers.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIDrivers.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIGather.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIGather.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTINextPhase.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTINextPhase.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIPatches.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIPatches.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ztiRunCommandHidden.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ztiRunCommandHidden.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIValidate.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIValidate.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG to \\192.168.36.208\Logs$\MININT-1H9O4H6\SMSTS.LOG]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\Debug\Netsetup.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\System32\wpeinit.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying log C:\MININT\SMSOSD\OSDLOGS\BDD.log contents to \\192.168.36.208\Logs$\MININT-1H9O4H6\BDD.LOG]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Powershell script returns the exception "Cannot index into a null array"

Similar Messages

Maybe you are looking for