Produkt:
Cognos Controller 10.2.1
Microsoft Windows 2008 R2 Server

Issue:
In the list of data sources in Cognos Controller Configuration is more databases than in the list that is shown for the Cognos Controller user when he log on to the Cognos Controller application with his Cognos Controller client program.
The Controller Configuration program was started on server as a normal user.
Solution:
When you start Controller Configuration program on the Windows server, you must start it with “Run as Administrator” to make it read the udl file from folder C:\Program Files\ibm\cognos\ccr_64\data\
Otherwise it will read the files from folder (and that can be different content):
C:\Users\%user%\AppData\Local\VirtualStore\Program Files\ibm\cognos\ccr_64\data\
The Controller services will only read the UDL files from the real C:\Program Files\ibm\cognos\ccr_64\data\ folder.
For security, New Windows OS forbids programs from writing to a variety of “sensitive” areas, among them the Windows folder and the Program Files folder. That includes all subfolders of Program Files, so this ban would be a hardship on older programs that store INI files or data files along with the program itself. To avoid disabling these programs, Windows OS lies to them. When they try to write to a banned location, it says “Sure, no problem!” but actually saves the data in a holding area called the Virtual Store. And when the program tries to read back the data it wrote, Windows Operating System slips in the data from the Virtual Store. The old program works fine, and other programs aren’t affected. A similar process handles programs that write to now-forbidden areas of the Registry.
Start – run command and enter %localappdata%\VirtualStore\ to see this users store.

http://www.pcmag.com/article2/0,2817,2325762,00.asp