TM1 Forum

I was out of the office yesterday and when I've come back today one of the servers is behaving very strangely.

There are loads of log files (50+) with numbers on the end and the tm1server file if filled (as are all the other log files) with an error message stating:

4332 [] ERROR 2016-12-02 11:44:40.870 TM1.Audit.PostProcessor Failed to open audit store in AppendRawStoreToAuditStore

Nothing has changed in the configuration file (a previous post with this message had an incorrect rawstore directory but mine is the same as the logging directory - a full file path and has not been changed recently).

I have saved the data on the server (it was working fine and users were logged in OK) and then shut the server down. It now won't start back up again. There are no error messages, it just seems to stop at "Done processing feeders" and shows as "stopped" in the admin console. I've tried deleting the feeder files.

Any ideas as to why this could be happening please? The server usually starts in a matter of seconds.

This is the full .cfg file parameters:

ServerName=08 Staffing Monitoring
DataBaseDirectory=E:\TM1 Servers\08 Staffing Monitoring\02 Data\
LoggingDirectory=E:\TM1 Servers\08 Staffing Monitoring\03 Log Files & Rawstores\
RawstoreDirectory=E:\TM1 Servers\08 Staffing Monitoring\03 Log Files & Rawstores\

AdminHost=*IP address redacted*
PortNumber=52753

AuditLogOn=T
AuditLogUpdateInterval=60
Language=eng
IdleConnectionTimeOutSeconds=3600
ClientPropertiesSyncInterval=180
Language=ENG
PerformanceMonitorOn=F
ProgressMessage=True
AuditLogMaxFileSize= 100 MB
AllowSeparateNandCRules=T
MaximumCubeLoadThreads= 3
MaximumViewSize=1500

The server has had the SSL update patch applied, correct?

tomok wrote:The server has had the SSL update patch applied, correct?

I believe so yes! Our application is hosted by a third party so their consultant has done this. I'm assuming this would impact all instances though, not just one? The others are working fine.

Have you checked for disc space issues?

Steve Rowe wrote:Have you checked for disc space issues?

Disk space looked fine - I copied it from our live server to test and got the same issues

I've managed to get it to start by restoring the data from a backup from last week and then copying all of the files in the data directory that had changed since then. I created a new log files folder (archived the old one) and re-started the server and it's loaded up fine.

I've absolutely no idea what the root cause was though to even work out whether it would happen again or not!

My guess would have been a corrupt log file. Have had this before and you mentioned creating a new logs folder which resolved.

Well it happened again this morning and it looks like I've found out what the culprit was... there was a default view on a control cube and when I've deleted that folder from the data directory it has started up fine.

Absolutely no idea why that would stop a server from starting but it has resolved the issue.

Well it happened again this morning and it looks like I've found out what the culprit was... there was a default view on a control cube and when I've deleted that folder from the data directory it has started up fine.

Absolutely no idea why that would stop a server from starting but it has resolved the issue.

I remember a while back, I spent good several days just to find out there was a view with a corrupted subset that would crash the server on startup!