It seems to me that the EXE's that have been installed into C:\Program Files (x86)[/b:a93f8af17d] really need to have the correct execution permissions set, preferably by the IBM Installation Manager.

Obviously, another option would be for the default installation location to be outside of the C:\Program Files[/b:a93f8af17d] and C:\Program Files (x86)[/b:a93f8af17d] directories. This could be a work-around, but its not really a comfortable solution.

So, currently I am educating myself about Windows 7 file and executable permissions to try and manually fix the problem. Any helpful suggestions gratefully received. If that fails, I'll try uninstalling and then re-installing outside of any virtual directories.

OK, so I found the following interesting resources about UAC in Windows 7 (and Vista):


Step 6: Create and Embed an Application Manifest (UAC)
http://msdn.microsoft.com/en-us/library/bb756929.aspx


How to launch a program always elevated under Vista UAC
http://sbs.seandaniel.com/2007/05/how-to-launch-program-always-elevated.html

As I understand it, the best solution might be for the Jazz server developers to create an Application Manifest (see reference 1), which would get installed by IBM Installation manager.

Reference 2 suggests that:

UAC is there for a reason, and I suggest only using this method if you know what you are doing and are ok with lowering the security level of your system!!

So now the warnings are out of the way, how do you create a shortcut that doesn't prompt you to run every time? Let's try creating one for the command prompt in Administrator Mode. Although this proceedure can be used for any application that is naughty for writing data into a system location, or that doesn't have a shim built for it to catch the data and write it into a better location.

... and then goes on to suggest a rather complex solution to the problem, involving a lot of manual steps.

In summary:

1. I would really like to see the development team solve this Windows 7/Vista issue, by providing an application manifest and/or storing writable files into a directory outside of the "Program Files" directory. Actually, splitting out the executable and configuration files in this way has parallels with the typical installation approach on a Linux (or UNIX) file system.

2. An alternative solution is to install Design Manager outside of the "Program Files" directory, for example C:\IBM[/b:a93f8af17d]. A user can select to do this using the currently available IBM Installer, although its not the default.

3. You can try the workaround I previously suggested:
a) Right-click Start>Accessories>Command Prompt, and then select Run as administrator.
b) Type cd C:\Program Files (x86)\IBM\DesignManager\server\server.startup.bat

However, considering the issues raised in , I think that option 2 is probably a better idea.

You should also be able to right click on the shortcut to start the server and choose the "Run as administrator" option instead of having to start a command prompt.

In the Windows 7 machine I use, I add the "Start" and "Stop" shortcuts to the desktop (first, find it in the Start menu, then right click and drag to the desktop -- you will be prompted to create a shortcut). Then to start and stop the server, I right click on the corresponding shortcut on the desktop and choose the "Run as administrator" option.

You should also be able to right click on the shortcut to start the server and choose the "Run as administrator" option instead of having to start a command prompt.

In the Windows 7 machine I use, I add the "Start" and "Stop" shortcuts to the desktop (first, find it in the Start menu, then right click and drag to the desktop -- you will be prompted to create a shortcut). Then to start and stop the server, I right click on the corresponding shortcut on the desktop and choose the "Run as administrator" option.

Thanks for your suggestion.

I agree with your advice, in principle, but it does not work for me. Only the "run as administrator" command prompt option works for me, when Design Manager is installed into C:\Program File s (x86).

The server fails to start up correctly if I select either Start Jazz Team Server or Start Jazz Team Server and CLM Applications, and Run as administrator.

Browsing to a page like https://ibm-k6pfrhmyfmm.lan:9443/jts/setup does not work.

I also tried creating shortcuts on the desktop, etc, as you suggested. This does not work for me.

However, selecting Command Prompt, and Run as administrator, etc... does start the server, and I can browse to https://ibm-k6pfrhmyfmm.lan:9443/jts/setup.

I have checked this several times for accuracy.

Could I have discovered a regression in RC2, in that case?

The only reason I can think of for this is that maybe the "Start in" directory is wrong in the shortcut. If you right click on the shortcut and choose Properties, please verify if your "Start in" directory is:

"C:\Program Files (x86)\IBM\DesignManagement\server"

with the quotes and the (x86).

The only reason I can think of for this is that maybe the "Start in" directory is wrong in the shortcut. If you right click on the shortcut and choose Properties, please verify if your "Start in" directory is:

"C:\Program Files (x86)\IBM\DesignManagement\server"

with the quotes and the (x86).

So far as I remember, this was not the case. I did not make any manual changes like that.

I have found this so frustrating that I have uninstalled Design Manager, and I will be re-installing it outside of the both "C:\Program Files\" and "C:Program Files (x86)".

To verify your suggestion, I would have to re-install to the same place, and probably go through all the same problems again. I would like to get past the installation stage, and get onto doing some work... So, I'm not keen on trying that again.

If the software had still been installed, then I would have verified your request, which is reasonable enough.

I confirm what Colin found .. I've had the same problems with Win 7 x64.
The shortcut appears fine, however running it with Admin priviledges does not exhibit the same behaviour as start cmd shell first (with Admin) and then running the start server bat file.

steve