TM1 Forum

Hi

I have my TM1 server running as a windows service.
If I make changes (like changing a value) and then Stop the service, TM1 automatically saves this change.

Is there a way to avoid this behavior???

Thanks

armas wrote: I have my TM1 server running as a windows service.
If I make changes (like changing a value) and then Stop the service, TM1 automatically saves this change.

Is there a way to avoid this behavior???

I can't see how; if there were such an option it would be way too easy to allow the service to shut down without doing the changes when you really wanted it to.

The only workaround that I can think of is to:
- Go to the Windows server task manager;
- Kill the process relating to the service; and
- Move the tm1s.log file out of its folder before you restart the service so that it won't reload.

There are 2 options that I can think of that are less severe than killing the process and moving the log file.

1/ Run tm1 as an application rather than a service, then on server load you will be prompted whether to load the log file or not

2/ Turn cube logging off!

(Although I have to say that loading log files to restore the server in the event of not saving before the server goes down is functionality that most people would want! I am curious as to why you would not want this default functionality?)

I am curious as to why you would not want this default functionality?)

Same here .)

I can't imagine why you would have this turned off ?


Olivier

armas wrote:Hi

I have my TM1 server running as a windows service.
If I make changes (like changing a value) and then Stop the service, TM1 automatically saves this change.

Is there a way to avoid this behavior???

Thanks

don't understand why you don't want this feature (i think this is a real feature .. not one of the bug features)

- some older versions didn't save the db when stopping the tm1service( you can downgrade )
- kill the tm1process with the taskmgr / killprocess command

the question is what's your objective..

ScottW wrote:There are 2 options that I can think of that are less severe than killing the process and moving the log file.
1/ Run tm1 as an application rather than a service, then on server load you will be prompted whether to load the log file or not
2/ Turn cube logging off!

Well, yeah... but it's a little late if he's already RUNNING it as a service and has logged the transactions, and needs to know how to do it for the current session.

As a future option it's certainly viable.

(Though I think you mean, say "No" when asked whether you want to save changes when you shut down the server. You're only asked the question on server load if the previous session crashed and the tm1s.log wasn't renamed, and therefore still exists.)

Thanks all

I had never really thought about doing this before until I sent a great amount of values to a certaing cube, through an Excel file, then lost that file and realized those values were not correct at all and I was not able to recall the exact locations where those values were sent.

Or probably there is a way to roll back??

Yep. If you're logged in as an administrator:
- Right click on the server
- Select "View Transaction Log"
- Fill out the details. Choose since when you wish to see changes, the cube and you can narrow the area of the cube down too but note it's a case of one element or all of them in each dimension.
- Note the server time is in GMT
- Click ok
- Go to Edit -> Select All
- Go to Edit -> Back out

They're all backed out.

Often a good idea to back the server up before you do this, particularly as it's the first time you've done it.

Cheers,
Martin