For past 9 months have had 32-bit BE and B-Commander (version april 2009) installed in the "Program Files (x86)/Bucket Explorer" folder. Both have worked fine. I backup files via scheduler to my S3 account daily with B-Commander.

I downloaded both 64-bit zip versions of BE64 and BC64 (BucketCommander64-2009100401.zip) versions and placed be64.exe and bc64.exe into a newly created "Program Files/Bucket Explorer" folder, and changed the file protection of the /Bucket Explorer/ subdir from readonly to read/write.

I configured and authenticated be64.exe, The "lic" file (Bucket Explorergregg.heacock.lic) appeared in the folder after authenticating BE, and subdirectory /config exists with xml files. BE64.exe is now working. I also configured uploads for BC (/config/BucketCommander.xml)

However, I cannot get bc.exe to run without it always asking "Do you want to use the trial version" (no) and "Do you want to activate the product" (yes). I enter email id and my Activation code. I would think it would authenticate the license, but every time it runs it asks the same questions.

How do I get bc.exe to stay authenticated so I can run it from command files? /config/BucketExplorer.xml has following lines in it: ("xxx" fields filled with appropriate info and keys)

<Authentication>
<CommanderSKey>xxxxxxxxxxxxxxxxxxxxxxx</CommanderSKey>
<Password>false</Password>
<Time>1266983891465</Time>
<Akey>xxxxxxxxxxxxxxxxxxxxxxxxxxxx</Akey>
<Skey>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</Skey>
<CommanderAKey>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</CommanderAKey>
<DontPromptUntil>1266983906103</DontPromptUntil>
<Name>gregg heacock</Name>
</Authentication>

I never had this problem with the 32-bit earler version which were installed from an exe file rather than a zip file. What must I do to get an authenticated 64-bit bc.exe to work?

- Gregg Heacock

Hi,
Now we are providing Bucket Explorer and Bucket Commander as separate product ,so you
need to also purchase bucket commander separately if you want to use and once you have purchased bucket commander then try to activate it with its own activation keys.You can not activate Bucket commander with activation keys of Bucket Explorer UI.


Thanks!

Okay - thanks for letting me know you have unbundled bucket commander (BC) from bucket explorer (BE). I purchased a license for BC.exe and activated it. Then I used the BE tools command "Edit Commander Config File" option and setup a config file for uploading some files, and email configuration. The files "bc-config.xml" & "bucketcommander.xml" are almost identical, sitting in C:\Program Files\Bucket Explorer\config subdirectory. (64-bit version)

When I ran bc.exe I now get "unable to read the credentials" message and cannot get past that. Got any ideas how to get this issue handled? I can't seem to get bucket commander (64-bit version) to work (upload files to my S3 account). What am I doing wrong? This has been frustrating me for several days.

from command prompt:

C:\Program Files\Bucket Explorer>bucketcommander64.exe -action:upload -authenticate:greggheacock -emailprofile:uploadcomplete -configfilename:config\bc-config.xml
Updating bucket explorer property file
Version : 2009.10.04.01

Unable to read the credentials.
------------------------------------------------------------------------------------------------------

Hiii,

you have specified nick name in xml with white spaces
<Name>gregg heacock</Name>

but you have specified nick name in command with out spaces as
-authenticate:greggheacock



try with this command
C:\Program Files\Bucket Explorer>bucketcommander64.exe -action:upload
-authenticate:"gregg heacock" -emailprofile:uploadcomplete -configfilename:config\bc-config.xml


Thanks!

I tried your suggestion making command line for BC.exe have my name with space. It didn't work. The command that used to work with April 2009 32-bit version of BC.exe that I used to have installed was this:

"C:\PROGRAM FILES (x86)\BUCKET EXPLORER\bucketcommander.EXE" -action:upload -authenticate:greggheacock -emailprofile:uploadcomplete

That command had my authenticate parrameter set to "greggheacock" and it worked. Next, the 64-bit version trials:

I erased my configfilename of "config\bc-config.xml" to take that out of the equation. Then I used Bucket Explorer to edit the config file, saving it as c:\program files\bucket exporer\bucketcommander.xml" which I think is the "default". Next I left the configfilename paramenter out of my command line. Below is what I ran from the command prompt with the 64-bit version (Oct 2009 version):

C:\Program Files\Bucket Explorer>"C:\PROGRAM FILES\BUCKET EXPLORER\bucketcommander64.exe" -action:upload -authenticate:greggheacock -emailprofile:uploadcomplete

Updating bucket explorer property file
Version : 2009.10.04.01

Unable to read the credentials.

When I ran it as you suggested with "authenticate:gregg heacock" this is the result:

C:\Program Files\Bucket Explorer>"C:\PROGRAM FILES\BUCKET EXPLORER\bucketcommand
er64.exe" -action:upload -authenticate:gregg heacock -emailprofile:uploadcomplete
Help:- -action:upload/download/copy/setaclstodefault -authenticate:nick-name -emailprofile:profilename -configfilename:configuration file name
Enter correct operation upload/download/copy/setaclstodefault

It didn't like that either. any other suggestions?

I really need to get BC working properly. I tried to go back to the April 2009 32-bit version, and it wouldn't allow me to re-install it - saying I need to run the current version.

Hello ,
Again you have entered the wrong command
as you have entered correct nick name but you have not specified name in double Quote.
Whenever any argument value contains white space , then it must be specified in as "Argument Value " . Because commander split the arguments by white spaces.
So here 'gregg' is being treated as the associated value of Authenticate argument, and 'heacock' is being treated as another invalid argument.
so your command is not working
C:\Program Files\Bucket Explorer>"C:\PROGRAM FILES\BUCKET EXPLORER\bucketcommand
er64.exe" -action:upload -authenticate:gregg heacock -emailprofile:uploadcomplete


please try with
C:\Program Files\Bucket Explorer>"C:\PROGRAM FILES\BUCKET EXPLORER\bucketcommand
er64.exe" -action:upload -authenticate:"gregg heacock" -emailprofile:uploadcomplete

Thank you so much, Rajkumari !
All is working now; seems kind of stupid & I missed the quotes thing.