Sage 100

Have you tried purging G/L history?

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------

Sorry @Brett Zimmerman.  Updating JE's after importing them.

@Wayne Schulz - You probably tire of people saying "You're the best" so I hope I don't put you over the edge.  You're the best KB searcher I know.

I will take a look at purging some history.  I am concerned about the JE to be updated.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!
------------------------------


Original Message:
Sent: 08-13-2025 08:35
From: Wayne Schulz
Subject: Error 16 file/Disc is full - v2022 ADV

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

We are looking into reverting back to Monday night's image, then purging the history to get under the data file size limitation.  Looks like the decision has been made for them to move to SQL

Sorry @Brett Zimmerman.  Updating JE's after importing them.

@Wayne Schulz - You probably tire of people saying "You're the best" so I hope I don't put you over the edge.  You're the best KB searcher I know.

I will take a look at purging some history.  I am concerned about the JE to be updated.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 08-13-2025 08:35
From: Wayne Schulz
Subject: Error 16 file/Disc is full - v2022 ADV

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

Restored an image from before the crash.  Now cleaning up the debris.

This can be moved out of Urgent Support.

We are looking into reverting back to Monday night's image, then purging the history to get under the data file size limitation.  Looks like the decision has been made for them to move to SQL

Sorry @Brett Zimmerman.  Updating JE's after importing them.

@Wayne Schulz - You probably tire of people saying "You're the best" so I hope I don't put you over the edge.  You're the best KB searcher I know.

I will take a look at purging some history.  I am concerned about the JE to be updated.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 08-13-2025 08:35
From: Wayne Schulz
Subject: Error 16 file/Disc is full - v2022 ADV

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

Almost done.  To purge data, you have to tweak the number of years to retain data.  So I changed from 15 to 3.  Purge ran.  Then I optimized the GL_detailposting table.  That took five hours.  I then ran the period close for the year BEFORE I changed the retention period back to 15.  It took about 20 seconds to realize my "OH Crap" moment.  We are restoring the image from 4 AM.  Almost out of the woods.

On a related note, I answered the brief survey sent after support closed the case.  I gave the analyst high marks but answered the question "Would I recommend Sage to a friend based on the support of the analyst" with a five.  I can I recommend the software based on a support case.  I also commented on the failure of the KB search to find the article that @Wayne Schulz posted above.  Within a couple hours, Sage calls me.  Chris Powers was on the other end.  Good conversation.   The irony of the KB complaint was Chris was UNABLE to find Wayne's document either, even after he pasted the KB ID into the search field.  I forward him the KB for further research....  And he mentioned that he is looking forward to the 2026 MOTM in San Diego.

Restored an image from before the crash.  Now cleaning up the debris.

This can be moved out of Urgent Support.

We are looking into reverting back to Monday night's image, then purging the history to get under the data file size limitation.  Looks like the decision has been made for them to move to SQL

Sorry @Brett Zimmerman.  Updating JE's after importing them.

@Wayne Schulz - You probably tire of people saying "You're the best" so I hope I don't put you over the edge.  You're the best KB searcher I know.

I will take a look at purging some history.  I am concerned about the JE to be updated.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 08-13-2025 08:35
From: Wayne Schulz
Subject: Error 16 file/Disc is full - v2022 ADV

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

If only there were a (sort of) independent group of Sage 100 consultants who regularly reviewed issues like this for the past 20 years and provided feedback to the publisher. It would be even better if publisher employees were invited to the annual convention to hear this feedback in person. Perhaps even have a session or two dedicated to feedback. Maybe someday this will happen. Until then, in the immortal words of Casey Kasem, "Keep your feet on the ground and keep reaching for the stars." Hey maybe we should form a group that does just this? Oh, wait. Never mind.

Almost done.  To purge data, you have to tweak the number of years to retain data.  So I changed from 15 to 3.  Purge ran.  Then I optimized the GL_detailposting table.  That took five hours.  I then ran the period close for the year BEFORE I changed the retention period back to 15.  It took about 20 seconds to realize my "OH Crap" moment.  We are restoring the image from 4 AM.  Almost out of the woods.

On a related note, I answered the brief survey sent after support closed the case.  I gave the analyst high marks but answered the question "Would I recommend Sage to a friend based on the support of the analyst" with a five.  I can I recommend the software based on a support case.  I also commented on the failure of the KB search to find the article that @Wayne Schulz posted above.  Within a couple hours, Sage calls me.  Chris Powers was on the other end.  Good conversation.   The irony of the KB complaint was Chris was UNABLE to find Wayne's document either, even after he pasted the KB ID into the search field.  I forward him the KB for further research....  And he mentioned that he is looking forward to the 2026 MOTM in San Diego.

Restored an image from before the crash.  Now cleaning up the debris.

This can be moved out of Urgent Support.

We are looking into reverting back to Monday night's image, then purging the history to get under the data file size limitation.  Looks like the decision has been made for them to move to SQL

Sorry @Brett Zimmerman.  Updating JE's after importing them.

@Wayne Schulz - You probably tire of people saying "You're the best" so I hope I don't put you over the edge.  You're the best KB searcher I know.

I will take a look at purging some history.  I am concerned about the JE to be updated.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 08-13-2025 08:35
From: Wayne Schulz
Subject: Error 16 file/Disc is full - v2022 ADV

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

Almost done.  To purge data, you have to tweak the number of years to retain data.  So I changed from 15 to 3.  Purge ran.  Then I optimized the GL_detailposting table.  That took five hours.  I then ran the period close for the year BEFORE I changed the retention period back to 15.  It took about 20 seconds to realize my "OH Crap" moment.  We are restoring the image from 4 AM.  Almost out of the woods.

On a related note, I answered the brief survey sent after support closed the case.  I gave the analyst high marks but answered the question "Would I recommend Sage to a friend based on the support of the analyst" with a five.  I can I recommend the software based on a support case.  I also commented on the failure of the KB search to find the article that @Wayne Schulz posted above.  Within a couple hours, Sage calls me.  Chris Powers was on the other end.  Good conversation.   The irony of the KB complaint was Chris was UNABLE to find Wayne's document either, even after he pasted the KB ID into the search field.  I forward him the KB for further research....  And he mentioned that he is looking forward to the 2026 MOTM in San Diego.

Restored an image from before the crash.  Now cleaning up the debris.

This can be moved out of Urgent Support.

We are looking into reverting back to Monday night's image, then purging the history to get under the data file size limitation.  Looks like the decision has been made for them to move to SQL

Sorry @Brett Zimmerman.  Updating JE's after importing them.

@Wayne Schulz - You probably tire of people saying "You're the best" so I hope I don't put you over the edge.  You're the best KB searcher I know.

I will take a look at purging some history.  I am concerned about the JE to be updated.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 08-13-2025 08:35
From: Wayne Schulz
Subject: Error 16 file/Disc is full - v2022 ADV

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

I can't tell you how much I appreciate knowing that others struggle with searching on the KB! I'm about at the point where I don't even look anymore - I just throw it out there and one of you master searchers manages to find it.

Almost done.  To purge data, you have to tweak the number of years to retain data.  So I changed from 15 to 3.  Purge ran.  Then I optimized the GL_detailposting table.  That took five hours.  I then ran the period close for the year BEFORE I changed the retention period back to 15.  It took about 20 seconds to realize my "OH Crap" moment.  We are restoring the image from 4 AM.  Almost out of the woods.

On a related note, I answered the brief survey sent after support closed the case.  I gave the analyst high marks but answered the question "Would I recommend Sage to a friend based on the support of the analyst" with a five.  I can I recommend the software based on a support case.  I also commented on the failure of the KB search to find the article that @Wayne Schulz posted above.  Within a couple hours, Sage calls me.  Chris Powers was on the other end.  Good conversation.   The irony of the KB complaint was Chris was UNABLE to find Wayne's document either, even after he pasted the KB ID into the search field.  I forward him the KB for further research....  And he mentioned that he is looking forward to the 2026 MOTM in San Diego.

Restored an image from before the crash.  Now cleaning up the debris.

This can be moved out of Urgent Support.

We are looking into reverting back to Monday night's image, then purging the history to get under the data file size limitation.  Looks like the decision has been made for them to move to SQL

Sorry @Brett Zimmerman.  Updating JE's after importing them.

@Wayne Schulz - You probably tire of people saying "You're the best" so I hope I don't put you over the edge.  You're the best KB searcher I know.

I will take a look at purging some history.  I am concerned about the JE to be updated.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 08-13-2025 08:35
From: Wayne Schulz
Subject: Error 16 file/Disc is full - v2022 ADV

I think you "buried the lead" as they say with " The detail posting table is huge (total of 16, third panel below)" and I'm unsure if you're acknowledging the issue with 16 segmented files or trying to find a workaround for it.

On the surface the (non chatgpt) answer seems to be that Sage has a soft limit of 16 segmented files and after that YMMV about what happens.

See:There are segmented data files for some data files

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number, Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT