11-29-2011 12:32 PM
I wonder if this somehow relates to using the administrator account. Could you try using an "user" account (that has admin privileges)?
12-01-2011 07:52 AM
I tried with another user account which has the administrator rights but it didn't change anything: the keys are still created at C:\Documents and Settings\UserName\Research In Motion and then the packager fails to find them.
12-08-2011 08:05 AM
So it seems that there was a mix between the languages of the path. The packager eventually made it to find the keys when I pasted them at C:/Dokumente und Einstellungen/Administrator/Local Settings/Application Data/Research In Motion
I had tried all in English, and all in German but not a mix of the two...
12-08-2011 09:41 AM
Thanks for following up with the solution. I'll pass this information along to our development team.
01-04-2012 01:24 PM
This virtual path approach doesn't make life easier when developing on machines under enterprise control. In my case the IT department at my organization remaps this location to a network share for easy access throughout the enterprise. Unfortunate byproduct of this is that I while the keys can be created bbwp cannot access the required path.
Why can't bbwp for tablet pick up the keys from the bin directory as is the case with the smartphone bbwp? Similar to the German case above there is no easy fix and I can safely bet that IT will not change their policies anytime soon.
Please advise if a build with more flexible sig key location support is possible.
01-04-2012 01:33 PM
The keys were moved out of the bin directory into user space because of the way Windows Vista/7 with UAC lock down the Program Files directory. Trying to write to the Program Files directory causes issues in many configurations.
I recommend reporting this use case via Issue Tracker (link in my sig), which we can then escalate to the development team. Please provide as much detail as possible and example directories if possible.
01-04-2012 02:03 PM