TM1 Forum

when launching Excel a user gets the following Error
"E10) Data directory not found."

Then if you try to connect to TM1 Error "cannot connect to Admin Server." appears.

All other users have no problems
I rebooted the PC and nothing.

I remember encountering this before but can't remember how to fix.

Usually this comes down to network access rights or problems resolving a network address. Something like this also happens if the TM1 or Perspectives license is missing or misplaced.

Eric wrote:when launching Excel a user gets the following Error
"E10) Data directory not found."

Then if you try to connect to TM1 Error "cannot connect to Admin Server." appears.

All other users have no problems
I rebooted the PC and nothing.

I remember encountering this before but can't remember how to fix.

Typically it's because either the wrong or no Admin Host server name is specified in the client's (Server Explorer) File -> Options dialog box. They may also have an invalid path to a local server data directory specified in there, but the "Cannot connect to Admin Server" error suggests that it's the former problem.

On occasion I've encountered situations where the DNS has gone funky as well, and entering the Admin Host server's IP address rather than name has rectified it.

Didn't think to check that the "E10) Data directory not found." threw me off.

As always THANK YOU Captain!

What is the this stupid Error code haunting me!

Another user is getting it, but they can actually connect to TM1. everything is working fine except the error comes up with excel launches!

Eric wrote:What is the this stupid Error code haunting me!

Another user is getting it, but they can actually connect to TM1. everything is working fine except the error comes up with excel launches!

I'd take a look in their .ini file; chances are that they have a dodgy data directory specified in there. Maybe just blow away the file altogether; the only price to be paid is the need to re-specify the Admin Host.

The data directory path is the one used if you were running a perspectives server. If the path does not exist then you get this error. Sometimes you can end up with a path defined on a machine without the perspectives licence. In this cases you can edit the ini file manually.
HTH

Alan, sorry no dice on deleting the ini. I tried the one in the all users directory and the users directory.

Steve, Yeah it was weird I took a look at it yesterday and it was odd, the perspective splash screen popped up and then the error occurred and then the client screen came up and everythign functions correctly, but every time TM1 launches the error occurs.

What should I edit in the ini file?

There can be .ini files all over the shop from the Docs and Settings folder to the TM1 install directory to the Windows directory.

Best bet is to do a search on tm1p.ini on your user's entire C:\. Open them up and where it says something like local server startup, set it to false instead of true.

Martin

What Martin said!

Sounds like your install is messed up though (or at least the method you are using to launch the client) if you are getting the Perspectives and the Client splash screen when you open TM1.

Have you got the add-in insalled and launching the xla from a shortcut or something?

[TM1]
UseHttpConnector=F
HttpProxyServerPort=
IntegratedLogin=F
UseHttpProxyServer=
DataBaseDirectory=C:\Program Files\Applix\Custom\TM1Data\PData <-------If the other parameter is F I don't think this matters.
AdvancedRulesEditor=T
HttpConnectorUrl=http://youraddress.com/tm1HttpProxy
HttpProxyServerHost=
AdminHost=XXXXX
Language=ENG
UseExcelCubeViewer=F
InProcessLocalServer=T
ConnectLocalAtStartup=F <-------MAKE SURE THIS IS F
LocalServerNetworkProtocol=tcp

Steve Rowe wrote: DataBaseDirectory=C:\Program Files\Applix\Custom\TM1Data\PData <-------If the other parameter is F I don't think this matters.

True that it doesn't matter for the server startup, but this directory will be where .xdi and .xru files are opened from and saved to if you use Excel to maintain your dims and rules.

Martin

Thanks all. Worked like a charm! If I get this error again and none of those solutions work I am going to flip out! How many times can the same error code pop up with different resolutions.