Repeated Data Store Warnings in Logs

phess_luckstone

We've been having some weird issues lately and every night around midnight we are seeing these errors on our base install of enterprise (11.1) Has anyone else seen this or knows what causes it?

 

Level	Time	Message	Source	Code	Time Elapse	UserName	Process	Thread	Method	Request ID
WARNING	May 9, 2025, 12:01:13 AM	Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52	Data Store	110586			3356	1

WARNING

May 8, 2025, 12:01:13 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

WARNING

May 7, 2025, 12:01:12 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

WARNING

May 6, 2025, 12:01:12 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

WARNING

May 5, 2025, 12:01:12 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

WARNING

May 4, 2025, 12:01:11 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

WARNING

May 3, 2025, 12:01:10 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

WARNING

May 2, 2025, 12:01:10 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

WARNING

May 1, 2025, 12:01:09 AM

Failed to create index on '{0}'. ERROR: syntax error at or near "," Position: 52

Data Store

110586

3356

1

 

TimWestern

Just spit balling here. Here are some things I would check.

1. On the server where you are running this, right click the drive that it runs on and see how much Disk space is left. 
2. If its not on a C Drive, but on a mapped one, do the same there.

3. Do the same for any database sources that your system has configured, any of them having insufficient space could cause such an error.
4. Do you have any nightly backups that might be running around this time? This looks oddly similar to an issue I saw when one of our unrelated services blew up its log folder and took up a lot of hard drive space making backup not possible.  (Its also similar to some issues I saw when a user tried to route to a particular location while the site was going through a backup/or was unresponsive during it.)
5. I'd be interested what you find in your webserver lo0gs for traffic around that time at night? maybe some request occurring around the same time is responsible for causing it?


(Note not saying this is all that it could be, b ut something here, makes me think 'drive space issue')