“Dimension Save Failed” after upgrade from 9.5 to ver 10

[nickykoller]

I cannot edit my Accounts dimension from Perspectives after upgrading.
As one saves, it gives the error “Dimension Save Failed” and then shuts down the database.
When it re-starts the saves are not there.

I have tried the following:
Logged on as another Admin user
Re-checked all “Admin rights” as the user logged in and to the dimension
Re-started all Tm1 Services
Edited another dimension fine with no problem
Tried to re-save or re-create the }Element Security cube for that dimension

I eventually went to my old ver 9.5 installation (still on another server), edited the dimension there fine, saved it and then copied the Accounts.dim file to my new ver 10 installation.
This did bring the changes in fine, but I still cannot edit or make changes on that particular dimension on my ver 10 installation.
The time stamp on both dim files was the same before I edited it.
It is a complex dimension that can't just be re-created from a source.

Any ideas

[Duncan P]

Are there any errors in the server log from the time at which the save was attempted?

[paulsimon]

Hi

As per Duncan's message, check the TM1Server log for any errors.

How are you editing the dimension? Are you using the Dimension Editor or a Dimension Worksheet?

Is the dimension on a Local Server or a network Server?

Although I don't think that there are any differences in format from version 9.5 to 10, it is probably best to restart the version 10 server immediately after first starting it with version 10. I recently had issues when converting v9.0 to v10.1.1. Making sure that I restarted the server immediately after first starting it, before doing any changes cured the problem. However, v9.0 to v10.1.1 is obviously a more dramatic upgrade because of the change to double byte character set, etc.

It is possible that the dimension has become corrupt, although this has only ever happened to me once in 14 years of using TM1. You can recover it by creating a dimension worksheet with the same name as the dimension in the directory point to by your local database path, and then editing the dimension in v9.5 (you will need to make a minor change, eg change the order of two elements). This should update the dim worksheet. You can then copy this to the v10 server and open the dimension worksheet and save it. This might cure the corruption. If you don't want to use the Dimension Worksheet route, you can export the dimension and re-import it. However, copying the .dim file while the v10 server is down and then restarting twice should do the same.

Regards

Paul Simon

[tomok]

I would look at "special" characters you may have used in element names. TM1 historically has been very lenient towards the characters you could use in element names, but it's possible they have clamped down a little more in version 10. Look for non-standard characters in the element names (anything other than a thru z, 0 thru 9). If you find some, try removing them and see if you can save in version 10. It may take a little bit of trial and error but that's the direction I would go.

[nickykoller]

Thanks for the feedback.
The server is a network server. I remote desktop onto the server to do the changes.
It happens of i manually edit using the Dimension Editor or run a Ti process.
i have recently found out that it is happening to another dimension now, although others are still fine.
the log file shows ABSOLUTELY nothing. I tried checking it a few times in different sequences.

I will take a look at the special characters - I think both dimensions have a few odd characters. Do the strange characters apply to just the name or the attributes too?