Unable to install TM1 on Windows8 Server R2.

小蚂蚱

Hello,

I am trying to install Cognos TM1 9.5.2 on Window8 server R2 Virtual Machine. After double clicking the setup.exe file it is giving me below error.

"Error 2738. Could not access VBScript run time for custom action."

We registered the vbscript.dll file but no luck. Is TM1 supports Windows8 ?

Thanks,
Santosh

a23742212

From :

If you have an IBM Support SR number (which you should have, as bugs should have been raised with IBM before being placed here), please note that in the subject too.

In addition to this, it would be appreciated if people would stop posting problems that their specific installation of TM1 is having in the Bugs forum.

The thread has been moved accordingly.

koko33777

santosh361 wrote:We registered the vbscript.dll file but no luck. Is TM1 supports Windows8 ?

There is of course a link to the supported environments in the . Did you check that first?

There's Windows Server 2008 Server R2 (which is supported) and Windows 8 (which is still in pre-release by Microsoft), and is not. "Windows Server 8" is currently only a codename (most likely it will end up being called Windows Server 2012, at a guess, and there certainly isn't an "R2" of it yet) so it's even less likely to be supported than Windows 8 (and, to clarify, is not supported).

gaohua5201

Thanks Alan for your response.

Sure will post new posts accordingly.

Here is my actual problem.

Currently we have two environments one is windows 2003 server and another 2008 server. 2003 server is installed with Cognos TM1 9.5.2 and 2008 server is installed with Cognos BI 10.1. Now we would like to have reporting on those TM1 cubes, when I try to create a data source connection in Cognos BI for TM1 it is giving error saying  failed to initialize TM1 API and unable to load tm1api.dll file.

Error : XMD-CON-0001 Connect failed with error message: TM1-ERR-0050 An attempt to initialize the TM1 API failed.

When I search I found that we need to install TM1 API in Cognos BI Server to connect TM1. But now it is unsuccessful.

Is there any other way to make this connection success ?

Thanks,
Santosh

str8899

santosh361 wrote:When I search I found that we need to install TM1 API in Cognos BI Server to connect TM1. But now it is unsuccessful.

TM1 9.5.2 supports Windows Server 2008 R2, it does not support the older Windows Server 2008, thus the Installer of the TM1 9.5.2 software will stop working on Windows Server 2008, see the IBM Technote 1495813:


To install TM1 9.5.2 on Windows Server 2008 fails with an error message "The operating system is not adequate for running IBM Cognos TM1"

santosh361 wrote:Currently we have two environments one is windows 2003 server and another 2008 server. 2003 server is installed with Cognos TM1 9.5.2 and 2008 server is installed with Cognos BI 10.1. Now we would like to have reporting on those TM1 cubes, when I try to create a data source connection in Cognos BI for TM1 it is giving error saying  failed to initialize TM1 API and unable to load tm1api.dll file.

Error : XMD-CON-0001 Connect failed with error message: TM1-ERR-0050 An attempt to initialize the TM1 API failed.

Is there any other way to make this connection success ?

The glue code between Cognos BI and TM1 is using the TM1 API, thus it most be able to locate and access it's DLL tm1api.dll

Newer versions of the Cognos BI software ship with and install the TM1 API files, older versions do not. If you are using an older version of the Cognos BI software you must install the TM1 9.5.2 software on the machine(s) running the Cognos BI Dispatcher to deploy the required but missing TM1 API files. But if these machines are running Windows Server 2008 you cannot install the TM1 9.5.2 software. In such a case, copy&paste the bin-directory of a working TM1 9.5.2 installation to the server machine(s) running the Cognos BI Dispatcher, register the DLL tm1api.dll using the DOS command regsvr32.exe as outlined in the IBM Technote 1398808 and add the full path to the bin-directory to your Windows system environment variable PATH as outlined in the IBM Technote 1516806.


Some IBM Technotes covering different aspects of this issue:


IBM Cognos 8 BI Connection to TM1 Data Source Generates TM1-ERR-0050


TM1-ERR-0050 error when creating data source connection to TM1 server from Cognos 8 BI


TM1-ERR-0050 setting up TM1 data source in Cognos Connection

https://www-304.ibm.com/support/docview ... wg21516806
'Could not load tm1api.dll due to: The specified module could not be found' when starting FAP service

wwpsy

After double clicking the setup.exe file

On 2008 Server, you should run the installer by right clicking the file and choosing Run as administrator

tianya369

Thanks for your response.

Sorry for the confusion, we are using Windows8 Server R2 and it is compatible with the Cognos TM19.5.2.

Also BI is Cognos 10.1, not sure if dll files will install with this version, I have searched whole Cognos folder but didn't find api.dll file.

We tried with run as administrator as well but no luck.

Thanks,
Santosh

wquyhytuoy

santosh361 wrote:I am trying to install Cognos TM1 9.5.2 on Window8 server R2 Virtual Machine. After double clicking the setup.exe file it is giving me below error.

"Error 2738. Could not access VBScript run time for custom action."

We registered the vbscript.dll file but no luck.

How did you register the DLL vbscript.dll ?


As outlined in the IBM Technote 1483889 ?

https://www-304.ibm.com/support/docview ... wg21483889
Error 2738: could not access VB script runtime for custom action

Cause
This error message indicates that the VBScript engine is not currently registered on the machine where the install/uninstall is taking place.

Resolution
The VBScript engine can be quickly registered by following these steps:

1. Run Command Prompt as administrator
1.1 Start Menu -> All Programs -> Accessories
1.2 Right click on Command Prompt and select Run as administrator

2. If you are using 64-bit version of Windows:
Type cd %windir%syswow64 into the Command Prompt and hit Enter

3. Type regsvr32 vbscript.dll into the Command Prompt and hit Enter



As outlined in the Nitro KB article Q10106 ?


Q10106 - ERRMSG: Error 2738. Could not access VBScript run time for custom action.

Resolution

The VBScript engine can be quickly registered by following these steps:

1. Run Command Prompt as administrator:
   1. Start Menu -> All Programs -> Accessories
   2. Right click on Command Prompt and select Run as administrator

2. Run the following command:
   If you are using 64-bit version of Windows:
   Type cd %windir%syswow64 into the Command Prompt and hit Enter

3. Type regsvr32 vbscript.dll into the Command Prompt and hit Enter.


If the above solution does not work, try the following alternative steps:

If you are using 64-bit version of Windows:

1. Run Command Prompt as administrator:
   1. Start Menu -> All Programs -> Accessories
   2. Right click on Command Prompt and select Run as administrator

2. Type the following command in the prompt: reg delete "HKCUSOFTWAREClassesWow6432NodeCLSID{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f, then hit Enter.

3. Next, you must also type the following command: c:windowssyswow64regsvr32 vbscript.dll, then hit Enter.

こ忘了隠藏ご

Thanks for your response.

We have already tried one on these solution i.e. First one registering the dll file and that is succeded but no luck.

Coming to altenative appoach i.e. Deleting registry keys as this is server I don't have access to modify them. I have requested my system administrator to change this but unfortunately he is not able to find that registry folder mentioned here. Not sure if this is same for windows server 8 r2 as well as they mentioned it for windows 7.

Once again thanks for information.

Thanks
Santosh

xiaomi1984

santosh361 wrote:Not sure if this is same for windows server 8 r2 as well as they mentioned it for windows 7.

Is there any possibility that at some point you will stop referring to a version of Windows That. Does. Not. Exist?

As I told you this above, and Vincent Hu told you over on MS TechNet, there is:
- Windows Server 2008 R2; and there is
- Windows Server 8, which is only a codename, is still in Beta, and does not have an R2 at this point.

If you are referring to Windows Server [size=200%]2008 R2, please refer to it as such.

If you are doing some experiment with the Beta version of Windows [size=200%]Server 8, which does not now and may never have an R2, and noting well that "2008" and "8" are not the same number and that one is supported and one is not, then please indicate that.

Because until you start referring to the actual, existing version that you are using, any answer that you get is going to be nothing more than a guess.

If you're asking people to spend the time to answer your questions, then please at least extend them the courtesy of taking the time to express the question both clearly and accurately.