Task Schduler that runs powershell script does not move the folder s3 bucket

Question

Task Schduler that runs powershell script does not move the folder s3 bucket

Sinem A 6

Hi all,

I have a PowerShell script that move a folder, that contains csv files and a txt, from shared folder to s3 Bucket. I have trouble about moving it to s3 bucket when it run automatically by task scheduler without giving any error. But when I run the task scheduler manually it can send to folder to s3.

Copy and paste did not work, I guess. Here is the screen shot of it;

Basically, script takes the xlsx files from shared folder (FileUpload), create new csv files from them in FileDownload and create a folder for new csv files and move folder to s3 bucket but as I mentioned job cannot move the folder to s3 bucket when it run automatically by task scheduler without giving any error. But when I run the task scheduler manually it can send to folder to s3.

Also “Run whether use is logged on or not” is selected in task scheduler.

Program: Powershell.exe
Add Arguments: -ExecutionPolicy Unrestricted -File "F:\Data Upload\ScriptConverttoCSVNew.ps1"

I have very limited information about both PowerShell and s3 bucket. Any help will be appreciated. I searched the problem but I could not find a solution

Thanks in advance
SinemA

4 answers

Your answer

Answer 1

Rich Matheisen 47,901

Under what account is the scheduled task run?
Are the two shares on the machine running the scheduled task, or are they located on some other machine?
Will the ACL on the shares (and the underlying directory structure) permit access to the account running the scheduled task?

There is no error checking or handling in your script. Do you know if there are any errors in its execution when it runs as a scheduled task?

Answer 2

Sinem A 6

The scheduled task is running by SERVICES which is a domain account.
Shared folder under a server and task scheduler under another server.
As I learned from our system supervisor, all the permission is given as full permission to the related accounts.

I checked the history of the task scheduler, I did not see any error during execution, unfortunately.

Thank you in advance

MotoX80 36,291 Reputation points

2022-03-18T12:33:24.933+00:00

Add a transcript to the script.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.host/start-transcript?view=powershell-5.1

Add Test-Path statements to verify that the script can see files and folder. Add statements to display the names of the files it is processing.

The scheduled task is running by SERVICES which is a domain account.

That statement is confusing. The Task scheduler is a Windows service which should be configured to run as the local SYSTEM account.

Individual tasks should be configured to run as an account that it related (required) to perform the process. Some tasks un as the interactive user, some run as SYSTEM. Tasks that need to access network shares should be configured to run as a domain account so that the other server can authenticate the account.
Rich Matheisen 47,901 Reputation points

2022-03-18T15:11:01.98+00:00

Please edit your original post and use the "Code Sample" editor to replace the code you posted. The Code Sample editor is the 5th icon from the left on the Format Bar, It's the one with the graphic "101 010".

The code in your original post (on line 3) assigns a value to the variable "$newname" but there are no other references to that variable. Also, on line 4, you assign a value to a variable "$newname2", but you do so right in the middle of "-replace" operation! On line 5 you have a "-replace" operator that's just dangling there with no subject. On line 10 you assign a value to a variable "$startindex", but lone 10 is a continuation of line 9 (which ends with a backtick)!

Is this really the code you're running? I doubt that the code you posted will run at all!
Sinem A 6 Reputation points

2022-03-19T12:08:21.427+00:00

The scheduled task is running by SERVICES which is a domain account. Yes, I do not know why but we have a domain account named SERVICES which runs this job.

I understand, I have changed the account that runs the job from SERVICES to SYSTEM.

Also added a line for Start-Transcript -Path "F:\transcript0.txt" -NoClobber.

But it gives access deny error, when I use SYSTEM account user, because there is 2 server inside the job.

First I should learn an account that can access the folders of the 2 different server.

After that, I will test again,

Thank you for your rely.
Sinem A 6 Reputation points

2022-03-19T12:10:22.72+00:00

I guess copy and paste the code did not work. I have not noticed that.
Thank you for your reply
I tried to add screen shot of it
MotoX80 36,291 Reputation points

2022-03-19T13:04:53.907+00:00

First I should learn an account that can access the folders of the 2 different server.

...I'm assuming that the F drive is a mapped drive to the second server...

Don't run the task as SYSTEM, it won't be able to authenticate to the second server. Run it as the domain account. Scheduled tasks do not go through the normal desktop logon process. The task may not have an F drive unless your script does a NET USE somewhere.

Put the transcript on the C: drive. Add a Get-Childitem and verify that the script can see the files.

Try using the UNC path (\Server2\Sharename) instead of the drive letter (F:).
Sinem A 6 Reputation points

2022-03-19T14:25:53.887+00:00
I used to SERVICES account to run the job, I have checked the folder permission for both servers for this account.

I saw that SERVICES has full control both of the servers,

After I scheduled the job, here is the first error inside the transcript.txt

PS>TerminatingError(New-Object): "Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 8000401a The server process could not be started because the configured identity is incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A)."
new-object : Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed
due to the following error: 8000401a The server process could not be started because the configured identity is
incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A).
At F:\Data Upload\ScriptExcelToCSV.ps1:24 char:14

$ExcelWB = new-object -comobject excel.application

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : ResourceUnavailable: (:) [New-Object], COMException

FullyQualifiedErrorId : NoCOMClassIdentified,Microsoft.PowerShell.Commands.NewObjectCommand
MotoX80 36,291 Reputation points

2022-03-19T14:51:06.557+00:00

Did you do something with Excel.Application? Find it in Dcomcnfg and check the identity tab. I don't have Excel installed so I can't share an image of what mine looks like.

What about the security eventlog, is there a logon failure for some account at the time you get that error?

Have you logged on to the server with that SERVICES domain account and successfully run the script?

Answer 3

Rich Matheisen 47,901

Is the scheduled task using the account SERVICE?

Does that account have permission to launch DCOM stuff?

Are you running this scheduled task on a server or workstation?

Instead of monkeying around with Excel a d COM, a better (i.e. portable, doesn't need Excel to be installed on the machine, more secure, etc.) way would be to install the PowerShell module **ImportExcel.*

Answer 4

Sinem A 6

Yes it seems that the problem is to create csv file step of the job by task scheduler

I am trying to use ImportExcel powershell module

Share via

Task Schduler that runs powershell script does not move the folder s3 bucket

4 answers

Your answer