web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Community site session details

Community site session details

Session Id :
Microsoft Dynamics RMS (Archived)

HQEventLog clearing

(0) ShareShare
ReportReport
Posted on by 522

It appears our HQEventLog table has become monstrous. When I try to go in to View Event Log in HQ Manager, I get an error that says I don't have enough storage (We have 32GB with 20 reserved for SQL). Can I go into SQL Management Studio (We are running SQL Server 2014 Standard) and delete entries from the table to get it back to a manageable size?

Thanks very much for any help!!

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    Am I reading this correctly Roger? You have a 32 GB hard drive running SQL 2014 Standard or did you mean to say 32 GB of Ram with 20 GB of memory allocated because the error is storage not memory. I just wanted to be sure I understood the question and I wouldn't recommend you delete anything just yet. Thanks

  • Roger Oakes Profile Picture
    522 on at

    My fault for being terribly unclear. Those numbers are RAM. We have terabytes of storage. Sorry about that.

  • Roger Oakes Profile Picture
    522 on at

    The HQEventLog Table is currently using about 2.3 GB of storage (63000000 Rows) and has never been cleared out in the history of our HQ use. It cannot be opened in HQ Manager because it gives an error that there is not enough storage for this operation.

    Thanks for any help!

  • Community Member Profile Picture
    on at

    Is the HQ manager accessing the log file from the server with terabytes of storage, or is someone trying to access this log file via HQ manager installed on another machine that doesn't have a terabyte of disk space to cache that much data?

    SQL ram configuration btw, is usually only 25% of total available memory so 20 GB of 32 I believe needs to be reconfigured. May not be a bad idea to simply stop and restart the SQL server services. At least until until you can get some assistance and direction with respect to optimizing and how to maintain SQL server.  You may find an optimization guide on customer source also. Because this is the companies data, I would sincerely recommend you obtain some professional help if possible Roger.

    Thank you for the reply also.  

  • Roger Oakes Profile Picture
    522 on at

    Have tried accessing from both clients and on the server itself, neither works. That is absolutely all this server does is run SQL server, all other domain functions are on other servers.

  • Community Member Profile Picture
    on at

    The memory is configured wrong and without doing a remote session, I can give you some basic ideas only.

    Whenever anyone starts suggesting deleting data, I get nervous and put the brakes on.

    Add the actual error/s in screen shots to this post please.

    In search type: %TEMP% then control A then delete everything.

    Run Disk cleanup and delete everything but the restore points (if applicable).

    Stop and restart the SQL Server.

    You could also try before restarting the SQL Server to rename the existing log to .old (don't delete anything).

    Anything past that you'll likely need to create a service request for or get some professional help.

    I would like to see the screen shot/s of the actual error from the server/the Windows Version and build of the server 32 bit or 64 bit /The SQL Version and build # 32 or 64 bit/The RMS version and build.

    Just out of curiosity, can you connect and test using the RMS sample database? (yes I know the log file isn't going to be the same size) I just would like to know if it works or not.

    Thanks

     

     

  • Verified answer
    Roger Oakes Profile Picture
    522 on at

    Thanks Freeman. Just to finish this up. The server is not configured to use 20 GB of RAM out of 32, it is configured to never use more than that. I have decided after some research to drop that amount down the next time I need to reboot the server. I went ahead and deleted the events from the HQEventLog table based on information obtained in other threads and it knocked the storage used by that table down from 3 GB to 40 MB. The event viewer in HQ manager now works fine so I'm going to mark this thread as closed. Thanks for all your attention and help to this question. I appreciate it very much!!

  • Community Member Profile Picture
    on at

    Hello Roger,

    I'd do a search if possible for the HQ optimization guide and or the CU 5 PCI compliance guide as both will have recommendations which you may apply to the SQL Server configuration and they're free which never hurts. I'm super happy to hear that knocked that file size down and fixed your issue. Nice execution, cheers Butch

  • Community Member Profile Picture
    on at

    This may also help remedy the other post with respect to duplicate transactions as a full log file or database can cause some pretty bizarre behaviors. I hope so, cheers.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics RMS (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans