Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script error #53

Open
tunavis opened this issue Aug 31, 2022 · 5 comments
Open

Script error #53

tunavis opened this issue Aug 31, 2022 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@tunavis
Copy link

tunavis commented Aug 31, 2022

What happened?

image

Receiving the follow error in veeam. Nothing in the logs file.

Steps To Reproduce

No response

VeeamNotify version

v1.0

PowerShell version

5.1

Veeam Backup & Replication build number

11.0.1.1261

Relevant log output

Log folder empty
@tunavis tunavis added the bug Something isn't working label Aug 31, 2022
@tigattack
Copy link
Owner

Could you please share your job log? This can be found at %ProgramData%\Veeam\Backup\<JOBNAME>\Job.<JOBNAME>.Backup.log.

Please remember to scrub any sensitive information.

I'm interested in the log output from the line stating Running post-job script onwards.

@sopleb
Copy link

sopleb commented Nov 17, 2022

I'm running into this same issue...

Running post-job script
[14.11.2022 10:17:27] <01> Info         Executing custom command [C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe], arguments [-NoProfile -ExecutionPolicy Bypass -File 'C:\VeeamScripts\VeeamNotify\Bootstrap.ps1']
[14.11.2022 10:17:27] <01> Warning      Post-job script terminated with exit code -196608

@sopleb
Copy link

sopleb commented Nov 17, 2022

Interesting... I removed the single quotes from the command and it worked fine...

[17.11.2022 00:04:47] <01> Info         Executing custom command [Powershell.exe], arguments [-File C:\VeeamScripts\VeeamNotify\Bootstrap.ps1]
[17.11.2022 00:04:57] <01> Info         Post-job script completed successfully

@tigattack
Copy link
Owner

Good catch @sopleb, thanks! That's interesting, I've not seen anything like that before.

Since I'm unable to reproduce the original issue, would you mind trying it again with the -NoProfile -ExecutionPolicy Bypass parameters and the full path to powershell.exe, but with no quotes on the Bootstrap.ps1 path?

It would also be useful to know what version of Veeam B&R you're running.

@sopleb
Copy link

sopleb commented Nov 18, 2022

Good catch @sopleb, thanks! That's interesting, I've not seen anything like that before.

Since I'm unable to reproduce the original issue, would you mind trying it again with the -NoProfile -ExecutionPolicy Bypass parameters and the full path to powershell.exe, but with no quotes on the Bootstrap.ps1 path?

It would also be useful to know what version of Veeam B&R you're running.

https://i.imgur.com/4ubYIHT.png

[18.11.2022 11:00:36] <01> Info         Running post-job script
[18.11.2022 11:00:36] <01> Info         Executing custom command [C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe], arguments [-NoProfile -ExecutionPolicy Bypass -File C:\VeeamScripts\VeeamNotify\Bootstrap.ps1]
[18.11.2022 11:01:08] <01> Info         Post-job script completed successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants