TM1 Forum

Guys,

We are running 9.5.2 and we are getting an issue when trying to run a TI process. So far I've been able to find the following:

1) If you use the server long name (for example tm1server.jims.com) TM1 is not able to resolves it.
2) If you use the short name tm1server the process runs fine.
3) Here is the issue we have a DNS alias for the server called tm1appdev.jims.com and even when using the short tm1appdev TM1 is not able resolve it.

We have tried all kinds of tests with the short alias name and we are able to ping it and resolve. Has anybody met this in the past? I'm going to raise this with IBM. If it turns out it is a bug I'll move this post to the bugs section, if not I'll leave it here,

Jim.

More info. It seems that the alias they have resolve to the machine long name rather than the short name which might explain why they don't work. It's still interesting to see why TM1 can't resolve long names,

Jim.

Hi Jim,

We are also facing the same issue. In our environmnet, the DNS name could be pinged only if we use a full DNS name and not the short name. Hence entering short DNS name in TI process does not help us. It would be really helpful if you could provide any updates on how to solve this issue? Thanks....

I raised a call with IBM about this. It is nothing to do with TM1. It's to do with how the server is setup. If you have a share on the box you are trying to reach use run on TM1 server and try to access that share using the DNS long name. You should find that it can't resolve the share name. If this is the case (which it should be) then show your IT deparment that you can't access DNS long names on the server and point them in the direction of the network (IP) settings on the server. They should be able to take it from there,

Jim.

jim wood wrote:It's still interesting to see why TM1 can't resolve long names

I'm about 99% certain that TM1 doesn't resolve anything. Just like with ODBC, where TM1 just uses the service to communicate with a database, so is the case with DNS resolving. TM1 just makes the appropriate call to the DNS service, with the short or long name, and expects back an IP address. If TM1 is having problems I am pretty sure there is something wrong with the customers naming scheme or service. Have you tested the names COMPLETELY, outside of TM1, to make sure all the names can be resolved. I would look here, not in TM1.

I think you were a bit late there Tomok. I had already told the OP that the problem is outside TM1 and what the solution is.

jim wood wrote:I think you were a bit late there Tomok. I had already told the OP that the problem is outside TM1 and what the solution is.

Whatever. It's not the first time I've had someone make a post while I've been in the middle of typing up a response.

tomok wrote:Whatever. It's not the first time I've had someone make a post while I've been in the middle of typing up a response.

It normally comes up with a preview of posts submitted while you were typing. Isn't this happening for you? If not I'll look in to why for you.

Hi Jim and Tom,

Thanks for your response. I just logged in to the TM1 server and tried to open the share using the DNS name, but it prompts for the windows authentication (I have admin access to the sever). But when I use the physical server name I can open the share without any issues.

Similarly if I use the physical server name in the TI process, it executes successfully. We are getting the error only if we use the DNS name in the TI process. But our requirement is to use the DNS name in the TI process. We are currently working with the DNS team regarding this issue. Please suggest any possible solution/workaround.

You have repliacted what said above. This has nohthing at all to do with TM1. You need to change your windows network settings. As I said once you point out to your IT department that you can't access the share using the DNS name it's over to them. This has nothing to do with TM1.