TM1 Forum

Hello everyone,

I have problems with TM1 cubes, I tried installing my server as a service and an application, I specified the data directory and I did the configuration (tm1s.cfg) right.
Now I can see my server show up in TM1 architect, but I don't see any cubes, rules, dimensions under the server.
The cube came in as one single file, and after I set up the server, they were decompressed into many files, they just don't show up in the TM1 architect.

Any help is greatly appreciated!

Hello,

Please check the following parameter in your cfg file:
DataBaseDirectory=.............
This have to point to your database directory in which you see your *.cub, *.dim, *.rux, *.pro, etc files.
Some zip program depcompress the files into nested directory and therefore your model is not in the current directory but one level below.

Can you log in to your model?
If yes then after the login please select the server name and you will see the database directory in the right pane (properties window).
You can turn on/off the properties window from View > Properties Window menu.

Regards,

Peter

Yeah, that's another issue I was gonna bring up.
So I can see the server in my architect, but when I double click it to log into the server, I get this error: Log in Failed: SecurityServiceNotFound.
This is when I use Integrated login. If I use TM1 login, I get the prompt, but the user name and password I set up when I install TM1 are not found.
Then I use admin and apple to log in, I can actually see something in architect, but are they the cubes, rules, dimensions for this particular server or Planning Sample?
I guess my question is if I log in with admin and apple, and my data directory is directed to my server (not the Planning Sample server), what do the files that shown up in the architect come from?

Thanks a lot!

Hello,

1.
"If I use TM1 login, I get the prompt, but the user name and password I set up when I install TM1 are not found."
You cannot add new user and pw to your TM1 model during the installation.
You can give only a server (Windows service) name and a model directory.

2.
If you see the Application: Planning sample and cube with plan_ starting then you logged in the sample database.

3.
You should ask a user name and a pw from your colleagues to login to your own model. (I suppose you do not want to crack it:))

4.
You can find detailed description about installing and removing TM1 services in the Remote Server Operation chapter in the Operation Guide (only 4 pages).

Best regards,

Peter

Hey Peter, I am doing a fresh install now.

The cube I got from our client is one single .cub file, it's about 10 MB, but every time I set up a server and point the data directory to this cube, after I open the architect, the planning sample files show up.
(When I do my custom installation, I chose custom data, so after I finish, I should only see TM1 admin, excel and TM1 myserver services)
My problem is even though I did not install the planning sample server, these files keep on appearing under myserver.
I tried installing under different paths, like C:\Program files\cognos\TM1, C:\TM1, etc. They did not work.
How can I get rid of these samples under custom\TM1Data?

I decide to run the server as a service and set it up during the installation

darkchild wrote:Hey Peter, I am doing a fresh install now.
The cube I got from our client is one single .cub file, it's about 10 MB, but every time I set up a server and point the data directory to this cube,

A singe cub file is not a model. You need to get at least the relevant dim files and probably you need the rux file for the cube as well.

darkchild wrote:I decide to run the server as a service and set it up during the installation

It is unnecessary and will not solve your issue.

Regards,
Peter

kpk wrote: A singe cub file is not a model. You need to get at least the relevant dim files and probably you need the rux file for the cube as well.

Hey Peter, how do I convert this single cub file into a model?
I thought when you created the server and specified the data directory, the server will load this single cub file and generate the necessary files.
We got this file from the client, but they don't really have good support system.
I am pretty sure this file is the reason why I don't get the required files.
Thanks!

darkchild wrote:Hey Peter, how do I convert this single cub file into a model?

There is no other way than 1) stop the server, 2) copy both the dim files and rule files into the same directory 3) start the server.

darkchild wrote:I thought when you created the server and specified the data directory, the server will load this single cub file and generate the necessary files.

No TM1 will not generate them.

darkchild wrote:We got this file from the client, but they don't really have good support system.

What is your role regarding this model? Are you an end user or a developer?

Basically we are trying to set up a TM1 server to host some files so we could use in reporting, but we have to use the client cube instead of the samples.
Now when I set up the server, I point to this client cube (ABC.cub, whose size is 10MB, and it's the only file we got) and once the setup is finished, I can see a lot of small .cub, .dim, etc files (whose sizes are 1KB, 3KB, etc, and they look just like these files in planning sample).
I am wondering where do they files come from? And if they are not generated from ABC.cub, how do I decompress ABC.cub, so I can load these files in TM1?

darkchild wrote:Basically we are trying to set up a TM1 server to host some files so we could use in reporting, but we have to use the client cube instead of the samples.
Now when I set up the server, I point to this client cube (ABC.cub, whose size is 10MB, and it's the only file we got) and once the setup is finished, I can see a lot of small .cub, .dim, etc files (whose sizes are 1KB, 3KB, etc, and they look just like these files in planning sample).
I am wondering where do they files come from? And if they are not generated from ABC.cub, how do I decompress ABC.cub, so I can load these files in TM1?

When you start a new TM1 server session it will automatically generate any system files that it needs. Generally, these will be cubes and dimensions starting with a } character. These help it keep track of things like the cubes, dimensions, chores and so on that exist on the server.

However they are all system objects. Data cubes like your ABC are created by the end user. The user has to create dimensions, then attach the dimensions into a cube. As they do so, new files will be created in the data directory; .dim files for the dimensions, .cub files for the cube itself, .rux files for the rules. Those ones, unlike the system ones, are not created automatically, but by the actions of the end user.

Peter is correct; to load that cube in a server session you need not only the .cub file but also the associated .dim files and the .rux file, if any. These are not stored within the .cub file itself. (In part because a dimension can be used in many cubes (or no cubes at all) and must therefore have a separate file to store its information in.)

It might be worthwile taking a look through the introductory documentation (the .pdfs) that came with TM1, specifically the ones relating to creating a cube.

Alan Kirk wrote: When you start a new TM1 server session it will automatically generate any system files that it needs. Generally, these will be cubes and dimensions starting with a } character. These help it keep track of things like the cubes, dimensions, chores and so on that exist on the server.

However they are all system objects. Data cubes like your ABC are created by the end user. The user has to create dimensions, then attach the dimensions into a cube. As they do so, new files will be created in the data directory; .dim files for the dimensions, .cub files for the cube itself, .rux files for the rules. Those ones, unlike the system ones, are not created automatically, but by the actions of the end user.

Peter is correct; to load that cube in a server session you need not only the .cub file but also the associated .dim files and the .rux file, if any. These are not stored within the .cub file itself. (In part because a dimension can be used in many cubes (or no cubes at all) and must therefore have a separate file to store its information in.)

It might be worthwile taking a look through the introductory documentation (the .pdfs) that came with TM1, specifically the ones relating to creating a cube.

Hello Alan, I have gone through the documentation several times, I did notice the cube we got was pretty bizarre.
We did not create the cube, we got the cube from the client. It's huge compared to the kind of cube files we see in planning samples and it has no associated dimension nor rule files.
You think it might be that the client forgot to pack these files with it? Because we have received other cubes before, they usually come with .dim, .rux and the tm1s.cfg and tm1s.lic, etc
Thanks a lot for helping!

darkchild wrote: Hello Alan, I have gone through the documentation several times, I did notice the cube we got was pretty bizarre.
We did not create the cube, we got the cube from the client. It's huge compared to the kind of cube files we see in planning samples

That's because the planning samples only contain sample data, and not much of it. "Live" .cubs will easily run to tens or hundreds of megabytes, even gigabytes.

darkchild wrote:and it has no associated dimension nor rule files.
You think it might be that the client forgot to pack these files with it?

I think that is a distinct possibility.

darkchild wrote:Because we have received other cubes before, they usually come with .dim, .rux and the tm1s.cfg and tm1s.lic, etc

I'm not too sure what they're doing sending licence files to third parties, but then again I'm not quite clear on what your role is there. However at a minimum (assuming that the cube had no rules) you would need the .dim files. If you tried to load the .cub files without them then, depending on version and if I recall correctly, you'll probably see an error in the server logs indicating that the dimensions can't be found.

Alan Kirk wrote:

darkchild wrote:Because we have received other cubes before, they usually come with .dim, .rux and the tm1s.cfg and tm1s.lic, etc

I'm not too sure what they're doing sending licence files to third parties, but then again I'm not quite clear on what your role is there. However at a minimum (assuming that the cube had no rules) you would need the .dim files. If you tried to load the .cub files without them then, depending on version and if I recall correctly, you'll probably see an error in the server logs indicating that the dimensions can't be found.

My role is to install the TM1 server and the load the cube from our clients on VM, so we can do development on it.
About the license files, what I meant was that we have received similar projects before. The package usually comes with many .cub, .dim, .rux files, as well as the tm1s.cfg and tm1s.lic files, so our job was pretty simple.
We just create a server and point the data directory to this location and then we can see these files in TM1 architect, then we can create data source in cognos.
This time we only get this one cube, in addition to the deployment files for cognos, so I tried to set it up like we used to, but apparently something is not quite right.

Another problem is I can't create service or application after I finish the TM1 installation. I create shortcut for "tm1s.exe" on desktop (error: can't locate data directory) and I use "tm1sd.exe" in command prompt (the service shows up in MMC, but when I turn the service on, error 1067).

I am totally lost here because I followed everything from the manual and guide, so could you help me identifying the problem, I am also contacting the client to ask about the cube.
Thank you both very much!

darkchild wrote:

Alan Kirk wrote: I'm not too sure what they're doing sending licence files to third parties, but then again I'm not quite clear on what your role is there. However at a minimum (assuming that the cube had no rules) you would need the .dim files. If you tried to load the .cub files without them then, depending on version and if I recall correctly, you'll probably see an error in the server logs indicating that the dimensions can't be found.

My role is to install the TM1 server and the load the cube from our clients on VM, so we can do development on it.

I can't really help you with any specifics relating to the use of a VM; I don't really believe in them for TM1. Potentially more trouble than they're worth IMHO. But on more general issues...

darkchild wrote: This time we only get this one cube, in addition to the deployment files for cognos, so I tried to set it up like we used to, but apparently something is not quite right.

That would be the absence of the .dim and possibly .rux files. Also they'd need to send you the various }ElementAttribute... cubes and dimensions if they've created attributes for the dimensions.

darkchild wrote:Another problem is I can't create service or application after I finish the TM1 installation. I create shortcut for "tm1s.exe" on desktop (error: can't locate data directory)

It's not enough to create a shortcut to the application, you need to provide the shortcut with arguments so that it knows where the database is. See my article "Introductory "How To" guide for installing TM1 Servers" (http://forums.olapforums.com/viewtopic.php?f=21&t=1352) for some information on how to specify those in the shortcut icon.

darkchild wrote:and I use "tm1sd.exe" in command prompt (the service shows up in MMC, but when I turn the service on, error 1067).

Don't know what that is off the top of my head, but there should be more information in the Windows logs. However I'd double check that the database folder and server name specified in the tm1s.cfg file is correct for your system, and that the server name shown in the .cfg file is the same as the one that you specified when you installed the service.

Of course it may be something else entirely.

darkchild wrote: My role is to install the TM1 server and the load the cube from our clients on VM, so we can do development on it.
About the license files, what I meant was that we have received similar projects before. The package usually comes with many .cub, .dim, .rux files, as well as the tm1s.cfg and tm1s.lic files, so our job was pretty simple.
We just create a server and point the data directory to this location and then we can see these files in TM1 architect, then we can create data source in cognos.
This time we only get this one cube, in addition to the deployment files for cognos, so I tried to set it up like we used to, but apparently something is not quite right.

Another problem is I can't create service or application after I finish the TM1 installation. I create shortcut for "tm1s.exe" on desktop (error: can't locate data directory) and I use "tm1sd.exe" in command prompt (the service shows up in MMC, but when I turn the service on, error 1067).

I am totally lost here because I followed everything from the manual and guide, so could you help me identifying the problem, I am also contacting the client to ask about the cube.
Thank you both very much!

Hello both starting TM1 as an application and service is described in details (STEP by STEP) in the operation guide:

operational_guide wrote: 1. Open the install_dir\bin directory in Windows Internet Explorer.
2. Right-click Tm1s.exe.
3. Select Create Shortcut.Windows creates Shortcut to Tm1s.exe in the install_dir\bin directory.
4. Right-click Shortcut to Tm1s.exe.
5. Select Properties.The Properties window opens.
6. Click the Shortcut tab.The Target field on this tab contains the full path to Tm1s.exe.
7. In the Target field, add the -z flag and specify the full path to the directory containing the Tm1s.cfg file for the server.
For example, -z C:\TM1\salesdata indicates that the Tm1s.cfg file for the server resides in the C:\TM1\salesdata directory.
Note: If the path to the directory contains any blank spaces, enclose the entire path with double quotes. The contents of the Target field should resemble the following:
"C:\Program Files\Cognos\TM1\\bin\tm1s.exe" -z C:\TM1\salesdata
8. Click OK to save the shortcut.

Have you edited the Target field?

operational_guide wrote: To install a TM1 server to run as a Windows service, use the following command line format:
tm1sd.exe -install parameters
The following table lists the available parameters.
Required/Optional Description Parameter
-n Required
Name of the TM1 Server. This will become the Windows service name as shown when you display the properties of an installed service.
-z Required
Data directory that contains the tm1.cfg file for the TM1 database.
-u Optional
Valid user name for the computer on which you are working. Use one of the following formats:
● Domain and user name in the format Domain\username. For example, entp\jsmith.
● User name for a local user account.
If you do not provide a user name, the current user account is used by default.
-w Optional Password for the above account.
For example, the following command line installs the sdata TM1 server as a Windows service for the current user.

tm1sd.exe -install -n sdata -z C:\Program Files\Cognos\TM1\Custom\TM1Data\SData

1. Open a command prompt.
2. Change to the TM1 bin directory. This is required to be able to start tm1sd.exe.
3. Type your own command tm1sd.exe -install sdata C:\Program Files\Cognos\TM1\Custom\TM1Data\SData

It is advisable to start TM1 as an application first. It is easier to find out the problem which is usually:
a) the CFG file cannot be found at the defined path
b) the CFG file contain incorrect path of the database directory

Regards,
Peter

Yes, I have followed the manual and guide down to the T.
If I use tm1s.exe, I make sure I create a shortcut on the desktop, and specify the location of the .cfg file, the location of the data directory, the Admin host, port number and the server name are optional.
If I use tm1sd.exe, I make sure I specify the name of the new server, the path to the data directory, the user name and the password are optional.
Now I can confirm these small .cub, .dim, .rux files are actually from the planning sample.
I am waiting for the client to get back to me.
But I might have more questions tomorrow.
Thank you so much for your help today.

I got my request back today, our client did send us the incomplete package, so now I have the server up and running, and all the cubes, dimensions and rules are showing up in the TM1 architect.
Now I've got another problem, the client also sent us the deployment package for cognos, now I've set up the Data Source Connection and Content Connection, I can't create a report within that package.
Even the metadata is not available.
The error is: Unable to find the data source 'ABC' in the content store.
I know TM1 source is trickier than other source, so other than selecting TM1 as the data source (usually we use OLE DB), any other configuration I should do?
Thanks!

I guess I need to define my data source the same as our client, so I re-import the package and give the exact same name as in the error.
Now I have another error: The cube ("ABC") does not contain a measure dimension.
And this cube is the single cube we received yesterday.

TM1-ERR-0003: The cube ("ABC") does not contain a measure dimension.

What does this mean? Do I need to create a dimension if the package we got from our client does not have one?
I am desperate here.

darkchild wrote:TM1-ERR-0003: The cube ("ABC") does not contain a measure dimension.

What does this mean? Do I need to create a dimension if the package we got from our client does not have one?
I am desperate here.

A measures dimension means nothing to TM1 as such. However TM1 still offers you the option of designating one dimension as the Measures one for systems which require cubes to have one. You do that by right clicking on the cube and selecting Properties. You can then select the most appropriate dimension to be the measures dimension (and the time dimension if you want). In a cube which stores GL balances, the chart of accounts dimension would typically be the Measures one.

Once you set a measures dimension that way, it's stored in the }CubeProperties system cube.