We have just started to use "Manage Software Distribution Packages". When uploading files we get a warning "File uploads in progress". That warning doesn't go away. We have even tested with small files (less than 50KB) located on the BES server itself and using the local console to bypass potential FW-problems Still the upload doesn't seem to finish. Version 8.1.617.0
Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Pinned topic Upload files to Software Distribution Packages
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-27T17:46:11Z at 2013-02-27T17:46:11Z by SystemAdmin
BenKus 27000468FT399 Posts
Re: Upload files to Software Distribution Packages2011-09-02T05:02:47ZThis is the accepted answer. This is the accepted answer.Look under "Setup" and make sure you have deployed the Fixlets including downloading and registering the server download plugin.
Re: Upload files to Software Distribution Packages2011-09-02T08:44:51ZThis is the accepted answer. This is the accepted answer.Thanks Ben!
These fixlets where all listed as non relevant.
The relevance clause for "Setup" was incorrect. Made a custom copy without the incorrect relevance check, installed and everything is fine now.
SystemAdmin 110000D4XK562 Posts
Re: Upload files to Software Distribution Packages2011-09-26T20:02:58ZThis is the accepted answer. This is the accepted answer.I had this issue, but my problem was that the BES plugin service was not running as the Active Directory service account that had rights to the database. In our case, the DB server is a separate box, and we use NT auth on the service accounts. If you simply deploy the plugin service and install the upload service plugin via fixlets, it can only start them as local system. Change service login account, problem solved.
CheleCuca 2700074HDD1 Post
Re: Upload files to Software Distribution Packages2014-05-09T23:18:17ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
+2 to the service login account solution. After changing it from local system to the correct AD account name all started to work.
thanks for posting the solution!