Recent Topics
-
UNSOLVED PA 19.00.57 (and earlier) Duplicate files possible in .pa archive in some cases.
Tech Support3 -
Fast Ring: PowerArchiver 2019 19.00.51/54/57
Tech Support6 -
UNSOLVED GUI: In need of a complete overhaul
Tech Support3 -
UNSOLVED GUI: move label
Tech Support3 -
UNSOLVED GUI: too much frames
Tech Support2 -
UNSOLVED PowerArchiver shell extensions possibly crashing windows explorer.exe
Tech Support10 -
UNSOLVED Encrypt files inside archive that has already been created [.zipx]
Wishlist3 -
UNSOLVED PA 19.00.51 / Access Violation
Tech Support7 -
SOLVED PA 19.00.51 - bug / unwanted code execution
Tech Support8 -
SOLVED Strange file size seen in 2019 portable
Tech Support5 -
SOLVED Fast Extract large files directly to target directory
Wishlist4 -
UNSOLVED Forums: double Search option in the settings (left side hamburger menu)
Tech Support1 -
SOLVED Serpent-256 Encryption for PAE/PAE2
Wishlist14 -
UNSOLVED Moving Files in to a 7Zip archive
Tech Support2 -
UNSOLVED hang when using the Test function with 7z archives
Tech Support5 -
UNSOLVED Some buttons in "Modern Look" are too small
Translations3 -
Fast Ring: PowerArchiver 2019 19.00.30/31/32/33/39/40/41/43/44/46/47/48/49
Tech Support23 -
UNSOLVED Searching for the specific Regkeys needed to default new installations in Modern Windows 10 not dark view
Tech Support2 -
UNSOLVED E-Mail problem
Tech Support7
Scheduling nightmares
-
I’ve written a vbs script to archive weblog files. The script works fine standing alone but when trying to schedule using SQL Server command line job it informs me that it cannot compress files of this type. The type is a .log but it reported the error for a .txt file as well.
I’ve tried using windows scheduler but this is playing up with its usual fuss over the run as account, it’ll only run under my account but my password is not fixed. SQL Server is the way forward and I’m hoping someone else may be using this method and have resolved any issues.
-
There has to be something in the way SQL command line works which in turn messes up your vbs script. I have absolutly no experience there so I cant be of much help, but I would check SQL server help for more info on command line and if you need to do anything special to pass command line strings.
