Local Server Start Problem.

[telula]

Hello,
I am having problems starting the local server. I have copied 2 files Data and Worksheets in C:\TM1Local.
Q1. Should the data dictionary be C:\TM1Local ? or C:\TM1Local\Data or C:\TM1Local\Worksheets?
Q2. I am getting Client's password is invalid when we have integrated login.

Can anyone help?

[Alan Kirk]

Hello,
I am having problems starting the local server. I have copied 2 files Data and Worksheets in C:\TM1Local.
Q1. Should the data dictionary be C:\TM1Local ? or C:\TM1Local\Data or C:\TM1Local\Worksheets?

It should be wherever your .cub and .dim and other files are. It will be whatever you set as the Local Server Data Directory in the TM1 Options dialog of Perspectives. If the local server doesn't find any existing cube and dimension files there, it'll create the necessary system ones, leaving you to create all of the data ones.

Q2. I am getting Client's password is invalid when we have integrated login.

Given that the IntegratedSecurityMode parameter is set in the tm1s.cfg file, and it's been well established from past posts that a local server will ignore the .cfg file when it loads, it's equally safe to assume that Integrated Login isn't going to work with a local server. That being the case, you need to revert to standard TM1 security. If it creates a "blank" data model as described above (that is, there is no pre-existing }Clients dimension, etc) you'll have to log in with the automatically defined Admin account with the password of Apple, then create your own logins and assign passwords.

[Alan Kirk]

Given that the IntegratedSecurityMode parameter is set in the tm1s.cfg file, and it's been well established from past posts that a local server will ignore the .cfg file when it loads, it's equally safe to assume that Integrated Login isn't going to work with a local server. That being the case, you need to revert to standard TM1 security. If it creates a "blank" data model as described above (that is, there is no pre-existing }Clients dimension, etc) you'll have to log in with the automatically defined Admin account with the password of Apple, then create your own logins and assign passwords.

I'll correct myself in one respect there; when a Local server starts, assuming that this really is a "local server" and not "a server that you just happen to be running as an application or a service on the local machine" (which is quite a different thing), the first time you fire it up it should automatically log you in as Admin. No password should be required.

[telula]

Well i seem to get it working by copy the Client Properties cube onto my C Drive from Production.
But there is a problem with the log files-It says "Error opening the log file"...what should I do?

[tomok]

Well i seem to get it working by copy the Client Properties cube onto my C Drive from Production.
But there is a problem with the log files-It says "Error opening the log file"...what should I do?

Does the logging directory as specified in your TM1.cfg file exist on your local machine?

[Alan Kirk]

Well i seem to get it working by copy the Client Properties cube onto my C Drive from Production.
But there is a problem with the log files-It says "Error opening the log file"...what should I do?

Does the logging directory as specified in your TM1.cfg file exist on your local machine?

She claims that it's a local server, as opposed to a server which is running on the local machine. Local servers ignore the settings in the tm1s.cfg file, as I mentioned earlier. That includes the logging directory parameter. (I just re-confirmed that that's still the case in a 9.5.1 session.)

[telula]

which is safe to conclude then that I dont have a local server.
So do I change the following details in my cfg file? my input is between the **

[TM1S]
ServerName=*mycomputername*
DataBaseDirectory=*C:\Tm1Local*
loggingdirectory=*C:\TM1Local\Logging*
AdminHost=*mycomputername*
ServicePrincipalName=HTTP/*mycomputername*

[Alan Kirk]

which is safe to conclude then that I dont have a local server.

Yes, very safe. No idea how I could have come to that conclusion with a subject heading like "Local Server Start Problem".

So do I change the following details in my cfg file? my input is between the **

[TM1S]
ServerName=*mycomputername*
DataBaseDirectory=*C:\Tm1Local*
loggingdirectory=*C:\TM1Local\Logging*
AdminHost=*mycomputername*
ServicePrincipalName=HTTP/*mycomputername*

Does the folder C:\TM1Local\Logging even exist, or are you just relying on the computer to create it for you?

[telula]

Well I have created that directory. So are the rest of the changes ok?

[Alan Kirk]

Well I have created that directory. So are the rest of the changes ok?

Nothing stands out as a major problem.

Some other possibilities:
- Another server session is already running and pointing to the C:\TM1Local\Logging directory for its log file. If that's the case the other session will have a lock on the file;
- Some companies lock down (most of) the C:\ drive so that you can't write to it. That seems unlikely if you were previously able to copy over the Client Properties cube.
- A virus scanner could be getting a lock on the log file. This will usually crash the server rather than generating an error message.
- The .cfg file that you've edited may not be where the server is expecting to see it. If you installed the server as a service, you would need to have specified the path to the .cfg file in the -z parameter when the service was installed. If you're running it as an application, it should be in the -z parameter of the shortcut that you use to launch the service. These issues are discussed in this thread.
- You may have mistyped the folder name. Best to copy the name from the address bar in Windows Explorer and paste it into the .cfg file to be sure.