<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communityhub.sage.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sage 300 Support and Insights</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub</link><description>Trusted Sage 300 product knowledge, news, and tips from Sage experts.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 17 Feb 2026 00:55:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub" /><item><title>The impact of Read-only mode on Sage 300 Intelligence Reporting upon the expiration of the Subscription Licenses</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-intelligence-reporting-upon-the-expiration-of-the-subscription-licenses</link><pubDate>Tue, 17 Feb 2026 00:55:45 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:71ac1c04-1056-4ee4-a9c0-c51c6a174163</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19871</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-intelligence-reporting-upon-the-expiration-of-the-subscription-licenses#comments</comments><description>&lt;p&gt;Following on from an earlier post about &lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages"&gt;&lt;strong&gt;Sage 300 Subscription Expiration messages&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, &lt;/strong&gt;we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for each module.&lt;/p&gt;
&lt;p&gt;Herewith our findings for the &lt;strong&gt;&lt;u&gt;Intelligence Reporting Module.&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;At the time of our testing, we found that all the Intelligence Reporting options remained available and functioned without any restrictions when in read-only mode.&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;img style="max-height:363px;max-width:873px;" height="363" src="https://communityhub.sage.com/resized-image/__size/1746x726/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1771289657353v1.png" width="873" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19871&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>Sage 300 E-invoicing Malaysia Module - PU3 - Audit table</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-e-invoicing-malaysia-module---pu3---audit-table</link><pubDate>Wed, 11 Feb 2026 03:22:56 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:e8976437-8569-424b-a330-6ad92895d0fb</guid><dc:creator>Meng Yuen Ang</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19865</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-e-invoicing-malaysia-module---pu3---audit-table#comments</comments><description>&lt;p&gt;In Sage 300 EI module PU3, there is a EIOAUD table which contain the audit trail of the E-invoice transaction.&lt;/p&gt;
&lt;p&gt;In EIODOC table, we can find out the current status of the invoice. However, if user perform refresh/send in EI Outgoing processing screen, there will be status change of the invoice. In EIOAUD table, we are able to trace the status change.&lt;/p&gt;
&lt;p&gt;To explain, i will start with create and posting an invoice. After posting the invoice in AR Invoice with invoice number TEST0211, below is the result of the EIOAUD table where IDINVC=&amp;#39;TEST0211&amp;#39; which is the invoice number.&lt;/p&gt;
&lt;p&gt;Take note of the SEQUENCE , PPLTRANS, PPLSTATUS and PPLAPSTT column.&amp;nbsp; SEQUENCE means it&amp;#39;s the very initial status of the invoice, it usually is right after the invoice is being posted in their respective module and generated into EI module.&lt;/p&gt;
&lt;p&gt;&lt;img style="height:178px;max-height:178px;max-width:1499px;" height="178" src="https://communityhub.sage.com/resized-image/__size/2998x356/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779318649v1.png" width="1498" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Go to EI Outgoing processing screen,&amp;nbsp;select the invoice and send it. Below is the results of the query after i have send the invoice. Notice an additional row is created with SEQUENCE = 2. PPLTRANS , PPLSTATUS, PPLAPSTT ,PPLDATE1,PPLTIME1 are changed, i can understand that the invoice is being Sent and i am able to find out this action is done by who and when based on the AUDTDATE/AUDTTIME and AUDTUSER.&lt;/p&gt;
&lt;p&gt;&lt;img style="height:226px;max-height:226px;max-width:1572px;" height="226" src="https://communityhub.sage.com/resized-image/__size/3144x452/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779481806v2.png" width="1571" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;I perform refresh in EI Outgoing processing screen to see if there is any changes on the status for the invoice , and if there is, there will be additional audit trail being logged for that invoice. if the invoice status remain unchanged after the refresh, there will be no new audit trail for that invoice.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The invoice in my example have a status change, thus there is a new sequence created.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779742422v4.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;At this point, my invoice is still pending response from LHDN, thus the PPLAPSTT= 15.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:250px;max-width:1509px;" height="250" src="https://communityhub.sage.com/resized-image/__size/3018x500/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779663757v3.png" width="1508" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;I wait a few minutes and refresh again, the invoice is being rejected by LHDN. Notice that PPLAPSTT column = 16, which mean the status is rejected by LHDN.&lt;/p&gt;
&lt;p&gt;&lt;img style="height:104px;max-height:104px;max-width:1446px;" height="104" src="https://communityhub.sage.com/resized-image/__size/2892x208/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779822699v5.png" width="1445" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:270px;max-width:1543px;" height="270" src="https://communityhub.sage.com/resized-image/__size/3086x540/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779848847v6.png" width="1543" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;If user re-select the invoice and send again, what would happen to the audit trail&amp;nbsp; ? Let&amp;#39;s take a look at below.&lt;/p&gt;
&lt;p&gt;Firstly, i resubmit the invoice.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779963035v7.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Then we look at the EIOAUD table. Here we can see that the audit trail is still ongoing. You may observe that there is a new PPLTRANS value, and PPLAPSTT has become 1 which is &amp;#39;Sent&amp;#39; status.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Here we can understand that user has resend the invoice, thus there is a new submission ID being issued due to a new PPLTRANS value.&lt;/p&gt;
&lt;p&gt;&lt;img style="height:287px;max-height:287px;max-width:1531px;" height="287" src="https://communityhub.sage.com/resized-image/__size/3062x574/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1770779986342v8.png" width="1530" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Conclusion :&lt;/p&gt;
&lt;p&gt;That&amp;#39;s all from my example. This audit trail is beneficial for partner / customer to investigate on what user have done on the E-invoice transaction which may help on trobleshooting/investigating.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19865&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/sage%2b300">sage 300</category><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/E_2D00_invoice%2bMalaysia">E-invoice Malaysia</category></item><item><title>The impact of Read-only mode on Sage 300 General Ledger upon the expiration of the Subscription Licenses</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---gl-module</link><pubDate>Tue, 27 Jan 2026 00:50:29 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:d196ec9b-b20b-4b80-9931-7828f5f76c86</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19847</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---gl-module#comments</comments><description>&lt;p&gt;Following on from an earlier post about &lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages"&gt;&lt;strong&gt;Sage 300 Subscription Expiration messages&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, &lt;/strong&gt;we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for each module.&lt;/p&gt;
&lt;p&gt;Herewith our findings for &lt;strong&gt;&lt;u&gt;General Ledger.&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;In read-only mode the G\L Periodic Processing folder will no longer be available&amp;hellip;&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;img style="max-height:303px;max-width:1032px;" alt=" " height="303" src="https://communityhub.sage.com/resized-image/__size/2064x606/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1769474648037v1.png" width="1032" /&gt;&amp;nbsp;&lt;/p&gt;
&lt;ol start="2"&gt;
&lt;li&gt;Under GL Accounts, the Create Accounts and Account Permissions icons will no longer be available whereas, within the Accounts and Budget Maintenance screens, all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the CLOSE button still visible.&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="padding-left:30px;"&gt;&lt;img style="max-height:327px;max-width:1057px;" alt=" " height="327" src="https://communityhub.sage.com/resized-image/__size/2114x654/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1769474693374v2.png" width="1057" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:578px;max-width:1070px;" alt=" " height="578" src="https://communityhub.sage.com/resized-image/__size/2140x1156/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1769474812489v4.png" width="1070" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;ol start="3"&gt;
&lt;li&gt;Under G/L Reports, the Optional Fields and Trans. Details Optional Fields icons will no longer be available.&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;img style="max-height:277px;max-width:1249px;" alt=" " height="277" src="https://communityhub.sage.com/resized-image/__size/2498x554/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1769474855790v5.png" width="1249" /&gt;&amp;nbsp;&lt;/p&gt;
&lt;ol start="4"&gt;
&lt;li&gt;Likewise, under G/L Setup, all the icons except the Optional Fields will still be available to view however, with in screens, all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the CLOSE button still visible.&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;br /&gt;&lt;img style="max-height:309px;max-width:1087px;" alt=" " height="309" src="https://communityhub.sage.com/resized-image/__size/2174x618/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1769474913437v6.png" width="1087" /&gt;&lt;/p&gt;
&lt;ol start="5"&gt;
&lt;li&gt;Under the G/L Transactions folder, the Post Batches icon will no longer be available whereas in the remaining Batch List and Journal Entry screens, all buttons normally visible, with exception of the CLOSE button, such as SAVE, ADD, DELETE, etc. will either be removed or greyed out.&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="padding-left:30px;"&gt;&lt;br /&gt; &lt;img style="max-height:663px;max-width:1234px;" alt=" " height="663" src="https://communityhub.sage.com/resized-image/__size/2468x1326/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1769474948498v7.png" width="1234" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19847&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>The impact of Read-only mode on Sage 300 Common Services upon the expiration of the Subscription Licenses</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-common-services-upon-the-expiration-of-the-subscription-licenses</link><pubDate>Wed, 13 Aug 2025 02:06:17 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:5bd30c83-f4c7-4775-b66c-369f7e4ffda8</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19537</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-common-services-upon-the-expiration-of-the-subscription-licenses#comments</comments><description>&lt;p&gt;Following on from an earlier post about &lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages"&gt;&lt;strong&gt;Sage 300 Subscription Expiration messages&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, &lt;/strong&gt;we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for each module.&lt;/p&gt;
&lt;p&gt;Herewith our findings for &lt;strong&gt;&lt;u&gt;Common Services.&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;In read-only mode the following 4 icons will no longer be available in &lt;strong&gt;Common Services&lt;/strong&gt;&amp;hellip;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;Service Centre&lt;/li&gt;
&lt;li&gt;Currency&lt;/li&gt;
&lt;li&gt;Optional Fields&lt;/li&gt;
&lt;li&gt;Multiple Contacts&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:287px;max-width:1107px;" alt=" " height="287" src="https://communityhub.sage.com/resized-image/__size/2214x574/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050217898v2.png" width="1107" /&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;ol start="2"&gt;
&lt;li&gt;Within the &lt;strong&gt;Company Profile&lt;/strong&gt; and &lt;strong&gt;Fiscal Calendar&lt;/strong&gt; screens, all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the CLOSE button still visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:597px;max-width:1248px;" alt=" " height="597" src="https://communityhub.sage.com/resized-image/__size/2496x1194/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050286144v3.png" width="1248" /&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol start="3"&gt;
&lt;li&gt;Under &lt;strong&gt;Scheduling&lt;/strong&gt;, both the &lt;strong&gt;Reminder list&lt;/strong&gt; as well as &lt;strong&gt;Schedules&lt;/strong&gt; options will still be displayed and one can also view the Schedule details however, yet again all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the CLOSE button still visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:485px;max-width:1361px;" alt=" " height="485" src="https://communityhub.sage.com/resized-image/__size/2722x970/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050313657v4.png" width="1361" /&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol start="4"&gt;
&lt;li&gt;Under &lt;strong&gt;Bank Services&lt;/strong&gt;, &lt;strong&gt;Bank Transaction Reports&lt;/strong&gt; and &lt;strong&gt;Bank Periodic processing&lt;/strong&gt; will no longer be available whereas within the &lt;strong&gt;Banks screen&lt;/strong&gt;, all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the CLOSE button still visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:342px;max-width:1303px;" alt=" " height="342" src="https://communityhub.sage.com/resized-image/__size/2606x684/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050409976v5.png" width="1303" /&gt;&lt;br /&gt;&lt;img style="max-height:645px;max-width:894px;" alt=" " height="645" src="https://communityhub.sage.com/resized-image/__size/1788x1290/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050444444v6.png" width="894" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Likewise, under &lt;strong&gt;Bank Setup&lt;/strong&gt;, all the icons will still be available to view however, with in screens, all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the CLOSE button still visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:351px;max-width:1221px;" alt=" " height="351" src="https://communityhub.sage.com/resized-image/__size/2442x702/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050476713v7.png" width="1221" /&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol start="6"&gt;
&lt;li&gt;All 6 &lt;strong&gt;Bank Setup Reports&lt;/strong&gt; will still be available and function as normal.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:411px;max-width:1289px;" alt=" " height="411" src="https://communityhub.sage.com/resized-image/__size/2578x822/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050511386v8.png" width="1289" /&gt;&lt;/li&gt;
&lt;li&gt;Under &lt;strong&gt;Bank Transactions&lt;/strong&gt; only the T&lt;strong&gt;ransaction History Inquiry&lt;/strong&gt; option will be available.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:342px;max-width:1287px;" alt=" " height="342" src="https://communityhub.sage.com/resized-image/__size/2574x684/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050542107v9.png" width="1287" /&gt;&lt;/li&gt;
&lt;li&gt;Likewise, under &lt;strong&gt;Tax Services&lt;/strong&gt;, the only available option will be &lt;strong&gt;Tax Reports&lt;/strong&gt;, and within Tax Reports, the only remaining report will be &lt;strong&gt;Tax Tracking&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:239px;max-width:1234px;" alt=" " height="239" src="https://communityhub.sage.com/resized-image/__size/2468x478/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050588014v10.png" width="1234" /&gt;&lt;br /&gt;&lt;br /&gt; &lt;img style="max-height:334px;max-width:1242px;" alt=" " height="334" src="https://communityhub.sage.com/resized-image/__size/2484x668/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1755050622663v11.png" width="1242" /&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19537&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>The impact of Read-only mode on Sage 300 Admin Services upon the expiration of the Subscription Licenses</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---admin-services</link><pubDate>Thu, 19 Jun 2025 05:24:14 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:8b45ecf6-0fd6-43a3-ae94-d2e8f4da3c91</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19498</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---admin-services#comments</comments><description>&lt;p&gt;Following on from an earlier post about &lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages"&gt;&lt;strong&gt;Sage 300 Subscription Expiration messages&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, &lt;/strong&gt;we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for each module.&lt;/p&gt;
&lt;p&gt;Herewith our findings for the &lt;strong&gt;&lt;u&gt;Administrative Services Module.&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;In read-only mode users will get a message similar to the below for all icons as well as reports under Administrative Services.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/7853.pastedimage1750310717424v1.png" /&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19498&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>Sage 300 Malaysia E-Invoicing - Missing Information in AP Vendor/AR Customer during submission</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-malaysia-e-invoicing---missing-information-in-ap-vendor-ar-customer-during-submission</link><pubDate>Wed, 09 Apr 2025 06:39:06 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:1c32fdb3-416e-42e6-bb13-d6ae0c0207fe</guid><dc:creator>Meng Yuen Ang</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19461</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-malaysia-e-invoicing---missing-information-in-ap-vendor-ar-customer-during-submission#comments</comments><description>&lt;p&gt;In Sage 300 Malaysia E-Invoicing,&amp;nbsp; posted transaction in Account Receivable, Account Payable and Order Entry will be available in EI Outgoing processing screen for submission purpose.&lt;/p&gt;
&lt;p&gt;*If client does not have Order Entry module , Account Receivable module will be used instead.&lt;/p&gt;
&lt;p&gt;According to Inland Revenue Board Malaysia requirement on E-Invoicing, there is a series of guidelines and requirement that we need to comply. We may find those information from their website.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I will be focusing on one of the major requirement that impact each transaction, which is the information required from your Customer or Vendor when submitting an E-invoice.&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;Below is a list we compiled from the guidelines that the information required Customer/Vendor as of April 9th 2025.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Compulsory information from Customer :&lt;/p&gt;
&lt;p&gt;*Note that everything listed below is required, the asterisk is for further explanation purpose at below.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744181486770v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Compulsory Information from Supplier :&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744181539609v3.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Hence, we need to ensure we fill in all the information according to the field in the AR Customer or Ap Vendors. Before E-invoicing is implemented in Malaysia, some users may have the habit to enter the address including Country, State, Postal Code in Address Line 1,Line 2, and Line 3.&lt;/p&gt;
&lt;p&gt;For Human ,we are able to identify what is the Postal Code, Country, State from the Address Line 1/2/3, but in order for Sage 300 to have these compulsory information such as City, State, Postal Code, Country for E-invoice submission, we have to enter in the field that is allocated for it respectively as we need to tell Sage 300 which fields are Country,State, or Postal code etc.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:546px;max-width:648px;" height="546" src="https://communityhub.sage.com/resized-image/__size/1296x1092/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744181719950v4.png" width="648" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;The Invoice will be rejected if any of these information is missing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What we could do :&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;If your transaction is from Account Payable or Account Receivable modules, you may proceed to Sage 300, and go to the respective AR Customers Screen or AP Vendors Screen, fill in the missing information, then perform a resubmit.&lt;/li&gt;
&lt;li&gt;If your transaction is a transaction from Order Entry,&amp;nbsp;using invoices from Order Entry for example,&amp;nbsp; during the posting of your invoices , the address information of the Customers are stored in a separate table in the database, which is OEINVH for OE invoices.
&lt;ol&gt;
&lt;li&gt;Thus, if CITY and Postal code are blank in AR Customer for that customer during the posting of your invoices, the BILCITY and BILZIP column will be blank in the OEINVH table for that invoice.&amp;nbsp;Thus , if you perform a resubmit after you filling in the CITY and POSTAL code in AR customers, it will still fail due to the information is still missing in the OEINVH table.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;What we can do here is complete the missing information in AR customers, then issue a new OE invoice which the information will be complete in OEINVH table. There will be no issue submitting the e-invoice after that.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Else if you are familiar with SQL, you may update the missing information for that invoice in the table via SQL. This is a workaround only for users who know what they are doing in SQL, else it is not recommended for common end users.&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19461&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/SAGE300">SAGE300</category></item><item><title>Sage 300 Web Screen - Undefined error during login</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-web-screen---undefined-error-during-login</link><pubDate>Wed, 09 Apr 2025 04:51:40 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:d07dcdda-d640-4842-8343-8c966c237d99</guid><dc:creator>Meng Yuen Ang</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19460</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-web-screen---undefined-error-during-login#comments</comments><description>&lt;p&gt;&lt;span&gt;in Sage 300 Web Screens&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The message, &amp;ldquo;Please correct the following issue(s): Undefined&amp;rdquo;, may appear when signing into Sage 300.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;img style="max-height:609px;max-width:510px;" height="609" src="https://communityhub.sage.com/resized-image/__size/1020x1218/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744174359733v1.png" width="510" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In many cases this is caused by a DNS name resolution issue. Also, for installations that use SSL certificates (HTTPS) the error may be attributed to improper application of the certificate on the server.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Steps to resolution:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;First verify if the same error occurs on the server. Basically, if the server has the error all computers accessing the page will also have the same error.&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span&gt;Open a browser on the server and enter the exact same address used to launch Sage 300. If the error appeared from the client computers when using the address, &lt;a href="http://abcompany.xx.com/Sage300"&gt;http://abcompany.xx.com/Sage300&lt;/a&gt; enter this address on the browser.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Enter user ID, password and select a company. &lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Click the Sign In button.&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If the error occurs on the server, this may indicate that &amp;ldquo;abcompany.xx.com&amp;rdquo; could not be resolved by the server. Consult with a network administrator to help assist with this issue. Meanwhile, to work around this error, ask a network administrator to add this line to the host file of the server.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;127.0.0.1 [full computer name of the server]&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Example: &lt;em&gt;127.0.0.1 abcomnpany.xx.com&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol start="4"&gt;
&lt;li&gt;&lt;span&gt;Reload the web page and try signing in. &lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In the case where a web page uses an address with https like &lt;a href="https://abcompany.xx.com/Sage300"&gt;&lt;strong&gt;https:&lt;/strong&gt;//abcompany.xx.com/Sage300&lt;/a&gt;&lt;strong&gt;, &lt;/strong&gt;and the same error occurs on the server, the network administrator has to ensure that the SSL certificate is also added to the Trusted Roots. Once this is done, the error should go away.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19460&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/SAGE300">SAGE300</category></item><item><title>Setting up Sage 300 for to display and capture data with Chinese characters</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/setting-up-sage-300-for-to-display-and-capture-data-with-chinese-characters</link><pubDate>Wed, 09 Apr 2025 04:23:22 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:d21a144c-d79a-4d6c-b049-0d6e60ae7ef1</guid><dc:creator>Meng Yuen Ang</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19459</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/setting-up-sage-300-for-to-display-and-capture-data-with-chinese-characters#comments</comments><description>&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;Part 1 : How to setup Chinese language User Interface:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;1. Ensure you have install the Chinese language packs via the Sage 300 installer.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:447px;max-width:592px;" height="447" src="https://communityhub.sage.com/resized-image/__size/1184x894/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744172895484v1.png" width="592" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;2. System locale and Region settings.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:515px;max-width:854px;" height="515" src="https://communityhub.sage.com/resized-image/__size/1708x1030/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744172941517v2.png" width="854" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;3. Login as the Users which language is set as Chinese in the Users setup.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:765px;max-width:685px;" height="765" src="https://communityhub.sage.com/resized-image/__size/1370x1530/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744172985280v3.png" width="685" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;Part&amp;nbsp;2 : How to capture data with Chinese Character:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;1. Database collation has to support Chinese characters , you may use Chinese_PRC_CI_AS&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:654px;max-width:736px;" height="654" src="https://communityhub.sage.com/resized-image/__size/1472x1308/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744173129142v4.png" width="736" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;This collation support multiple code set, which it can store Chinese language characters and English.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:619px;max-width:976px;" height="619" src="https://communityhub.sage.com/resized-image/__size/1952x1238/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744173187391v5.png" width="976" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;2. Input method&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I recommend to use highlighted input method below using input method and language below, as it can support both Traditional Chinese (commonly used in Taiwan and Hong Kong) , and Simplified Chinese.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:650px;max-width:1015px;" height="650" src="https://communityhub.sage.com/resized-image/__size/2030x1300/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744173282099v7.png" width="1015" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;3. With the input method and Database collation being setup, you may perform data entry in Sage 300 with Simplified Chinese/Traditional Chinese and English in Sage 300 without having the character becoming gibberish.&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;Traditional Chinese:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:646px;max-width:891px;" height="646" src="https://communityhub.sage.com/resized-image/__size/1782x1292/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744173472139v8.png" width="891" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;Simplified Chinese :&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:650px;max-width:901px;" height="650" src="https://communityhub.sage.com/resized-image/__size/1802x1300/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744173483545v9.png" width="901" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;Here it&amp;#39;s a summary :&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;System Locale = Simplified, China&lt;/li&gt;
&lt;li&gt;MSSQL Collation = Chinese_PRC_CI_AS&lt;/li&gt;
&lt;li&gt;Input method = RPC, 中文(&lt;u&gt;中华&lt;/u&gt;人民共和国)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;&lt;em&gt;This work for both Traditional and Simplified Chinese! Since Microsoft has include both code set in PRC.&lt;/em&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;Additional Scenario:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;1. I want to remain English User interface, but printing report with Chinese characters, turns out i am able to capture Chinese character data and view Chinese character in the UI, but&amp;nbsp;the reports print via Crystal report is having gibberish characters.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;Ans : This is because the .rpt file is not using the font that support Chinese characters.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;In the Sage 300 program folder, in each individual module, we may find the .RPT file within the module folder. For example , if you are signing in as a user which the language is being set as English in the Administrative service-&amp;gt; User, when printing a report, Sage 300 will use the .rpt file within ENG folder.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;If you are signing in as a user which the language is being set as Chinese simplified in the&amp;nbsp;&lt;span&gt;Administrative service-&amp;gt; User, when printing a report, Sage 300 will use the .rpt file within CHN folder.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;img style="max-height:259px;max-width:987px;" height="259" src="https://communityhub.sage.com/resized-image/__size/1974x518/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1744173822515v10.png" width="987" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;em&gt;&lt;/em&gt;If we use the Crystal report designer and view the design of the .rpt file , we can see that the font being used are different. Thus, you might have Chinese character becoming gibberish when printing a report using a user with English language user interface.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;At this point, you might have thought of customize all the .rpt file to a font that support Chinese character. It works but there is a tons of .RPT file within Sage 300.&lt;/span&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19459&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/SAGE300">SAGE300</category></item><item><title>Sage 300 Malaysia E-Invoicing/Singapore InvoiceNow - Network Connection Error/Operation Timeout Error</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-malaysia-e-invoicing-singapore-invoicenow---network-connection-error-operation-timeout-error</link><pubDate>Wed, 09 Apr 2025 03:34:57 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:d5206b82-387a-4357-aef7-6ea60831d0d1</guid><dc:creator>Meng Yuen Ang</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19458</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-malaysia-e-invoicing-singapore-invoicenow---network-connection-error-operation-timeout-error#comments</comments><description>&lt;p&gt;Sage 300 Malaysia E-Invoicing (EI), and Singapore Invoice Now (VV) module is a 4 corner model that Sage 300 EI/VV module is the Corner 1, and Corner 2 is Peppol access point provider.&lt;/p&gt;
&lt;p&gt;Which mean Sage 300 need to be able to establish connection with Corner 2 to perform E-Invoicing seamlessly via PEPPOL network.&lt;/p&gt;
&lt;p&gt;Often user encounter Network Connection error as below.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Screenshot of error message:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/8308.pastedimage1744170462569v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Assuming the environment has access to the Internet, and the HTTPS port is open, but still unable to perform E-invoicing feature successfully is often due to the connection to the Access Point provider is not being trusted.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The reason that the connection is not trusted is due to the SSL used by the Access Point provider is not being trusted in your Operating System.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;How do we solve this:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;1) First we need to find out ,what is the SSL being used by the Peppol access Point provider?&lt;/p&gt;
&lt;p&gt;Ans: We should understand the integration is done via an API hosted online by the PEPPOL Access point provider, thus there will be an URL given. We could use some online tools like SSLChecker , and using this tool, we are able to find out what is the Certificate Authority that issued the SSL.&lt;/p&gt;
&lt;p&gt;2) After finding what is the certificate authority of the SSL used by the provider , we can perform checking in the operating system by perform Run command and enter certlm.msc, this will launch the &amp;#39;Local Machine Certificate&amp;#39; management tools. Click on &amp;#39;Trusted Root Certification Authority&amp;#39; -&amp;gt; &amp;#39;Certificates&amp;#39;. From the Screen below, we are able to view what are the root certificate being installed in the machine.&amp;nbsp; Let&amp;#39;s assume the provider is using certificate from Entrust Certificate authority , you should not be able to view the respective entrust root certification authority is not being installed as if you are facing the Network Connection Error issue.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:568px;max-width:838px;" height="568" src="https://communityhub.sage.com/resized-image/__size/1676x1136/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/6116.pastedimage1744171232651v3.png" width="838" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;3.&amp;nbsp; From Step 1 , if we run the SSL checker, we are able to observe the SSL chain used by the Access point provider. We can see that it is using certificate which the issuer are Entrust Root Certification Authority - G2, and&amp;nbsp;&lt;span&gt;Entrust Root Certification Authority.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thus, we should have this two root certificate being installed in the trusted root certification authority to have the connection being trusted and establish connection successfully.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:573px;max-width:886px;" height="573" src="https://communityhub.sage.com/resized-image/__size/1772x1146/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/0285.pastedimage1744171443458v4.png" width="886" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:429px;max-width:909px;" height="429" src="https://communityhub.sage.com/resized-image/__size/1818x858/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/7450.pastedimage1744171569155v5.png" width="909" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;How do we get the root certificate and install it in our machine :&amp;nbsp;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;1. We can just google the &amp;lt;Certificate authority name&amp;gt; + Root certificate as the keyword in search engine to bring us to the download page of the root certificate.&lt;/p&gt;
&lt;p&gt;For Example :&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Search on google &amp;#39;CA name + root certificate&amp;#39; , we able to get the download page as the top results.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:198px;max-width:932px;" height="198" src="https://communityhub.sage.com/resized-image/__size/1864x396/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/5633.pastedimage1744171797415v7.png" width="932" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;In my example above, with the SSL Checker, i needed &amp;quot;E&lt;span&gt;ntrust Root Certification Authority - G2&amp;quot;, and &amp;quot;&lt;/span&gt;&lt;span&gt;Entrust Root Certification Authority&amp;quot; these 2 root certificate, thus i will only download the required root certificate as highlighted below. It will not works if you install the incorrect root certificate.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:302px;max-width:938px;" height="302" src="https://communityhub.sage.com/resized-image/__size/1876x604/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/2806.pastedimage1744171820324v8.png" width="938" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;2. How do i perform the installation.&lt;/p&gt;
&lt;p&gt;You may refer to this guides from Microsoft to perform the installation.&lt;/p&gt;
&lt;p&gt;&lt;a id="" href="https://learn.microsoft.com/en-us/skype-sdk/sdn/articles/installing-the-trusted-root-certificate"&gt;https://learn.microsoft.com/en-us/skype-sdk/sdn/articles/installing-the-trusted-root-certificate&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;3. After installing the missing certificate, proceed to Sage 300 Malaysia/Singapore E-invoicing module and the issue should be resolved.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;Notes :&amp;nbsp;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;1) The issue may not happen to everyone, as some organization has limit what are the root certificate being installed in the machine of their organization.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;2) The root certificate required is controlled by the PEPPOL access point provider , under circumstances of change of access point provider, or access point provider renewed their SSL with other certificate authority, you might face the Network Connection error again as if the Certificate authority has been changed and your machine doesn&amp;#39;t have the root certificate in the trusted root certificate authority store.&lt;/p&gt;
&lt;p&gt;3) Sometime user may feedback they have no issue accessing the URL in the browser, this is because browser has it own trusted root certification authority store, and it will be different than your trusted root certification authority store in your operating system.&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;strong&gt;Useful Reference:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Reference read on 4 corner model:&lt;/p&gt;
&lt;p&gt;&lt;a id="" href="https://www.imda.gov.sg/how-we-can-help/nationwide-e-invoicing-framework/invoicenow-technical-playbook"&gt;https://www.imda.gov.sg/how-we-can-help/nationwide-e-invoicing-framework/invoicenow-technical-playbook&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Reference read on Certificates and Trust:&lt;/p&gt;
&lt;p&gt;https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/certificate-trust&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19458&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/SAGE300">SAGE300</category></item><item><title>The impact of Read-only mode on Sage 300 upon the expiration of the Subscription Licenses - AR Module</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---ar-module</link><pubDate>Tue, 01 Apr 2025 01:06:18 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:f2fb1b52-9500-42b0-84cd-1b224bc0b828</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>4</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19455</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---ar-module#comments</comments><description>&lt;p&gt;Following on from an earlier post about &lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages"&gt;&lt;strong&gt;Sage 300 Subscription Expiration messages&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, &lt;/strong&gt;we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for each module. Herewith our findings for the &lt;strong&gt;&lt;u&gt;Accounts Receivable Module.&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;In read-only mode the following &lt;strong&gt;3 Customer Reports&lt;/strong&gt; will no longer be available&amp;hellip;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;National Accounts&lt;/li&gt;
&lt;li&gt;Statements / Letters / Labels&lt;/li&gt;
&lt;li&gt;Labels&lt;br /&gt;&lt;br /&gt;&lt;img alt=" " height="283" src="https://communityhub.sage.com/resized-image/__size/2664x566/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743469720406v1.png" width="1332" /&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;ol start="2"&gt;
&lt;li&gt;Under &lt;strong&gt;A/R Customers&lt;/strong&gt;, all options besides National Accounts will still be visible. Within screens, all buttons normally visible such as SAVE, ADD, DELETE, etc. will however be removed with only the close button still visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:843px;max-width:1316px;" alt=" " height="843" src="https://communityhub.sage.com/resized-image/__size/2632x1686/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743469811186v2.png" width="1316" /&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol start="3"&gt;
&lt;li&gt;In read-only mode the entire &lt;strong&gt;Periodic Processing&lt;/strong&gt; menu with all options will no longer be available.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:210px;max-width:1317px;" alt=" " height="210" src="https://communityhub.sage.com/resized-image/__size/2634x420/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743470004229v4.png" width="1317" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Under the &lt;strong&gt;Setup&lt;/strong&gt; Menu, all options besides Salespersons, Items and Optional Fields will still be visible. Within screens, all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the close button still visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:559px;max-width:1306px;" alt=" " height="559" src="https://communityhub.sage.com/resized-image/__size/2612x1118/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743470053419v5.png" width="1306" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Likewise, all &lt;strong&gt;Setup Reports&lt;/strong&gt; will be available excepts Salespersons, Items and Optional Fields reports.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:219px;max-width:1299px;" alt=" " height="219" src="https://communityhub.sage.com/resized-image/__size/2598x438/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743470190898v6.png" width="1299" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Under the &lt;strong&gt;Transactions Report&lt;/strong&gt; menu there are certain reports that are no longer available such as &amp;ldquo;aged&amp;rdquo; reports which create temporary records in database tables when executed. In AR these are&amp;hellip;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;Deposit Slips&lt;/li&gt;
&lt;li&gt;Customer Transactions&lt;/li&gt;
&lt;li&gt;Item Sales History&lt;/li&gt;
&lt;li&gt;Aged Trial Balance&lt;/li&gt;
&lt;li&gt;Aged Retainage&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;img style="max-height:188px;max-width:1308px;" alt=" " height="188" src="https://communityhub.sage.com/resized-image/__size/2616x376/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743470281697v7.png" width="1308" /&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;ol start="7"&gt;
&lt;li&gt;All icons besides the Post Batches are available under the &lt;strong&gt;Transactions&lt;/strong&gt; Menu but again only the close button will be visible with most buttons normally visible removed.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:572px;max-width:1297px;" alt=" " height="572" src="https://communityhub.sage.com/resized-image/__size/2594x1144/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743470400699v8.png" width="1297" /&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19455&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>Unlocking Growth: The Sage CRM Opportunity for Sage 300 Partners</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/unlocking-growth-the-sage-crm-opportunity-for-sage-300-partners</link><pubDate>Thu, 27 Feb 2025 06:53:11 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:3809f82b-37ee-43c8-9fff-cab44e5e9e95</guid><dc:creator>Sage CRM</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19437</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/unlocking-growth-the-sage-crm-opportunity-for-sage-300-partners#comments</comments><description>&lt;p&gt;&lt;img style="max-height:375px;max-width:500px;" alt=" " src="https://communityhub.sage.com/resized-image/__size/1000x750/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/2025_2D00_02_2D00_22-12.42.09.jpg" /&gt;&lt;br /&gt;TPAC South Africa 2025 (Feb 20-22) brought together Sage 300 partners, ISVs, and industry leaders to explore the latest innovations and opportunities in the Sage ecosystem. It was great to join Richard Jang in the keynote and have John Thomas join us virtually for one of the sessions.&amp;nbsp; One&amp;nbsp;theme from the event was the power of Sage CRM when integrated with Sage 300&amp;mdash;and the massive revenue potential this unlocks for partners.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A Reminder: Every Sage 300 Customer Has Access to Sage CRM&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Many Sage 300 partners aren&amp;rsquo;t fully leveraging one of the biggest growth opportunities available: Every Sage 300 customer is entitled to a free Sage CRM user license. That means you already have customers who can benefit from CRM&amp;mdash;if you introduce it as part of their existing Sage 300 solution.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why Sage 300 Partners Should Pay Attention to Sage CRM&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;&lt;em&gt;&lt;strong&gt;A Strong Commitment to Sage CRM&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;At TPAC, we reinforced Sage&amp;rsquo;s ongoing investment in Sage CRM, including product updates, a simplified licensing model from Sage CRM 2025 R1, and a focus on making CRM more accessible for Sage 300 users. Sage CRM is a proven, scalable solution with over 1,500 implementations across Africa &amp;amp; the Middle East.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Real-World Success: Sage CRM Driving Business Growth&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Several Sage 300 partners shared incredible success stories of businesses using Sage CRM to improve operations and drive revenue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A 300+ user CRM system managing the transshipment and tracking of goods across Zambia, Zimbabwe, South Africa, and Mozambique.&lt;/li&gt;
&lt;li&gt;A 100-user CRM solution for loan management across 16 retail stores in Jamaica&amp;mdash;a unique example of Sage CRM supporting a non-traditional industry.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Seamless Integration with Sage 300&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;Sage CRM isn&amp;rsquo;t just another add-on&amp;mdash;it&amp;rsquo;s a powerful extension of Sage 300, bringing customer and accounting data together so businesses can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Give sales teams real-time access to customer financials, including order history and credit status.&lt;/li&gt;
&lt;li&gt;Improve customer service by linking support cases to invoices, orders, and payments.&lt;/li&gt;
&lt;li&gt;Automate workflows, reduce manual data entry, and provide a 360-degree view of the customer.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;A Major Revenue Opportunity for Partners&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;By growing Sage CRM licenses within your Sage 300 customer base, you can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Increase recurring revenue through CRM subscriptions and support.&lt;/li&gt;
&lt;li&gt;Expand services by offering CRM implementation, customization, and training.&lt;/li&gt;
&lt;li&gt;Strengthen customer retention by providing a fully integrated ERP + CRM solution.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;The Road Ahead: Partner Enablement &amp;amp; Training&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;One of the biggest takeaways from TPAC was the need for more training and enablement. Sage 300 partners want live, instructor-led CRM training to help them position and implement the solution effectively. We&amp;rsquo;re working on ways to close the skills gap and provide better support for partners who want to grow their Sage CRM business.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Next Steps: Don&amp;rsquo;t Leave CRM Revenue on the Table&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re a Sage 300 partner, now is the time to start the CRM conversation with your customers. Many already have access to a Sage CRM license&amp;mdash;it&amp;rsquo;s up to you to show them how it can transform their business.&lt;/p&gt;
&lt;p&gt;Want to learn more? Let&amp;rsquo;s talk about how to start growing Sage CRM revenue within your Sage 300 customer base. Contact your Sage account manager!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19437&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>The impact of Read-only mode on Sage 300 upon the expiration of the Subscription Licenses - AP Module</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses</link><pubDate>Thu, 20 Feb 2025 04:22:17 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:627a7985-184b-46f7-8e53-eaeb0de85f86</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19418</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses#comments</comments><description>&lt;p&gt;Following on from an earlier post about &lt;strong&gt;&lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages"&gt;Sage 300 Subscription Expiration messages&lt;/a&gt;, &lt;/strong&gt;we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for the various modules. &lt;br /&gt;&lt;br /&gt;Herewith our findings when testing functionality in the the &lt;strong&gt;&lt;u&gt;Accounts Payable Module.&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;In read-only mode the entire &lt;strong&gt;Period Processing&lt;/strong&gt; menu, with all options, will no longer be available.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:253px;max-width:1350px;" alt=" " height="253" src="https://communityhub.sage.com/resized-image/__size/2700x506/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/6786.pastedimage1740025617822v1.png" width="1350" /&gt;&lt;/li&gt;
&lt;li&gt;Under the &lt;strong&gt;Setup Menu&lt;/strong&gt;, all options besides the &lt;strong&gt;Optional Fields&lt;/strong&gt; will still be visible. However, within screens, all buttons normally visible such as SAVE, ADD, DELETE, etc. will be removed with only the CLOSE button still visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:587px;max-width:1362px;" alt=" " height="587" src="https://communityhub.sage.com/resized-image/__size/2724x1174/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/8863.pastedimage1740025663007v2.png" width="1362" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Likewise, all &lt;strong&gt;Setup Reports&lt;/strong&gt; will be available excepts the &lt;strong&gt;Optional Fields&lt;/strong&gt; report.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:192px;max-width:1366px;" alt=" " height="192" src="https://communityhub.sage.com/resized-image/__size/2732x384/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/2577.pastedimage1740025712016v3.png" width="1366" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Under the &lt;strong&gt;Transaction Reports&amp;nbsp;&lt;/strong&gt;menu,&amp;nbsp;&amp;nbsp;certain reports are no longer available. These appear to be reports which,&amp;nbsp;when executed,&amp;nbsp;&lt;span&gt;write to table(s) to generate&lt;/span&gt;&amp;nbsp;e.g.&amp;nbsp;any &amp;ldquo;aged&amp;rdquo; reports. The database however remains accessible and, any missing reports, could therefore be replaced by custom reports as required.&lt;br /&gt;&lt;br /&gt;In AP these are&amp;hellip;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;Vendor Transactions&lt;/li&gt;
&lt;li&gt;Aged Payables&lt;/li&gt;
&lt;li&gt;Aged Cash Requirements&lt;/li&gt;
&lt;li&gt;Aged Retainage&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:219px;max-width:1375px;" alt=" " height="219" src="https://communityhub.sage.com/resized-image/__size/2750x438/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/6201.pastedimage1740025803881v4.png" width="1375" /&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;ol start="5"&gt;
&lt;li&gt;Like the Setup menu, most icons are available under the &lt;strong&gt;Transactions&lt;/strong&gt; Menu but, within screens, again only the CLOSE button will be visible and all buttons normally visible removed. The following 3 options are however no longer available in read-only mode&amp;hellip;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;Create Payment Batch&lt;/li&gt;
&lt;li&gt;Control Payments&lt;/li&gt;
&lt;li&gt;Post Batches&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:814px;max-width:1387px;" alt=" " height="814" src="https://communityhub.sage.com/resized-image/__size/2774x1628/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/4643.pastedimage1740025871128v5.png" width="1387" /&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;ol start="6"&gt;
&lt;li&gt;In read-only mode the following 3&lt;strong&gt; Vendor Reports&lt;/strong&gt; will no longer be available&amp;hellip;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;Letters / Labels&lt;/li&gt;
&lt;li&gt;Print T5018 (CPRS) Forms&lt;/li&gt;
&lt;li&gt;1099 Filing&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:286px;max-width:1387px;" alt=" " height="286" src="https://communityhub.sage.com/resized-image/__size/2774x572/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/0268.pastedimage1740025935894v6.png" width="1387" /&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;ol start="7"&gt;
&lt;li&gt;All options under &lt;strong&gt;Vendors&lt;/strong&gt; will still be available however, as in other screens, only the CLOSE button will be visible.&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:280px;max-width:1378px;" alt=" " height="280" src="https://communityhub.sage.com/resized-image/__size/2756x560/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/4073.pastedimage1740025980706v7.png" width="1378" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19418&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>Sage 300 Subscription Expiration messages.</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages</link><pubDate>Tue, 23 Jul 2024 08:20:10 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:2eb7c90d-23bb-43f4-9280-85df71900711</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19298</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/sage-300-subscription-expiration-messages#comments</comments><description>&lt;p&gt;We recently had a case where a customer complained that their subscription licenses expired, resulting in their system going into read-only mode during a rather busy period prior to year-end however they received no warning messages prior to the system becoming read-only.&lt;/p&gt;
&lt;p&gt;This prompted an investigation during which we confirmed what is supposed happen, as well as tested that this does indeed occur, and I thought to share this info which could be helpful to others.&lt;/p&gt;
&lt;p&gt;We have found that there are currently two possible scenarios.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;One which relates to older systems which still have a 60-day grace period as per the following article.&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;&lt;a href="https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924850098579&amp;amp;page=1&amp;amp;position=3&amp;amp;q=subscription"&gt;Error: &amp;quot;Your Sage 300 subscription has expired&amp;quot; when logging in&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;nbsp;The other scenario relates to newer releases which have a 45-day grace period as per this article.&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;&lt;a href="https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=220924460105946&amp;amp;page=1&amp;amp;position=0&amp;amp;q=subscription"&gt;Versions and Subscription Entitlement Process&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The first point which may need clarification is that &lt;strong&gt;&lt;u&gt;no warning messages are displayed prior to the license expiration date&lt;/u&gt;&lt;/strong&gt;. A set of warning messages are however displayed during the grace period on specific days based on a predetermined schedule as outlined below. &lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;It is important to note that warning messages are only displayed on the days listed in the schedule&lt;/strong&gt;&lt;/span&gt; and not on any dates in between.&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;For older systems with a 60-day grace period, the schedule for a license which expires on 28 April 2025, is as follows.&lt;/span&gt;&lt;/p&gt;
&lt;table width="381"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;&lt;u&gt;Expiry date&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="176"&gt;
&lt;p&gt;&lt;u&gt;Monday, 28 April 2025&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;&lt;u&gt;Day #&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;&lt;u&gt;# Days&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 1&lt;/p&gt;
&lt;/td&gt;
&lt;td width="176"&gt;
&lt;p&gt;Wednesday, 28 May 2025&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;30&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;30&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 1&lt;/p&gt;
&lt;/td&gt;
&lt;td width="176"&gt;
&lt;p&gt;Thursday, 12 June 2025&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;45&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;15&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 1&lt;/p&gt;
&lt;/td&gt;
&lt;td width="176"&gt;
&lt;p&gt;Friday, 27 June 2025&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;60&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;15&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;30 Days after expiry date:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:399px;max-width:592px;" alt=" " height="399" src="https://communityhub.sage.com/resized-image/__size/1184x798/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/6378.30days.png" width="592" /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;45 Days after expiry date:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:408px;max-width:593px;" alt=" " height="408" src="https://communityhub.sage.com/resized-image/__size/1186x816/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/4721.45days.png" width="593" /&gt;&lt;/p&gt;
&lt;p&gt;60 Days after expiry date:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:0px;max-width:0px;" alt=" " src="https://communityhub.sage.com/resized-image/__size/0x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/7444.60days.png" /&gt;&lt;img style="max-height:414px;max-width:608px;" alt=" " height="414" src="https://communityhub.sage.com/resized-image/__size/1216x828/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/pastedimage1743483146638v1.png" width="608" /&gt;&lt;/p&gt;
&lt;p&gt;When clicking OK on the 30-day and 45-day messages, the user can log in and the system will function as per normal however, when doing the same on the 60-day message, the user can still log in but now the system will be in read-only mode.&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;For later systems with a 45-day grace period and&lt;span&gt;&amp;nbsp;a license which expired on 06 May 2024,&amp;nbsp;&lt;/span&gt;the schedule would be as follows.&lt;/span&gt;&lt;/p&gt;
&lt;table width="382"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;&lt;u&gt;Expiry date&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;&lt;u&gt;Monday, 6 May 2024&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;&lt;u&gt;Day #&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;&lt;u&gt;# Days&lt;/u&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 1&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Sunday, 12 May 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;6&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;6&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 1&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Wednesday, 15 May 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;9&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;3&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 1&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Saturday, 18 May 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;12&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;3&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Wednesday, 22 May 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;16&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Sunday, 26 May 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;20&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Thursday, 30 May 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;24&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Monday, 3 June 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;28&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Friday, 7 June 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;32&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Tuesday, 11 June 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;36&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Saturday, 15 June 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;40&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Wednesday, 19 June 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;44&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;4&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="88"&gt;
&lt;p&gt;Message 3&lt;/p&gt;
&lt;/td&gt;
&lt;td width="177"&gt;
&lt;p&gt;Friday, 21 June 2024&lt;/p&gt;
&lt;/td&gt;
&lt;td width="55"&gt;
&lt;p&gt;46&lt;/p&gt;
&lt;/td&gt;
&lt;td width="61"&gt;
&lt;p&gt;2&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;img style="max-height:1260px;max-width:1212px;" alt=" " height="1260" src="https://communityhub.sage.com/resized-image/__size/2424x2520/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/2158.message-list.png" width="1212" /&gt;&lt;/p&gt;
&lt;p&gt;Similar to the previous scenario, when clicking OK on the first 2 messages displayed during the grace period, the user can log in and the system will function as per normal however, when doing the same on the third message displayed on day 46 and later, the user can still log in but the system will now be in read-only mode.&lt;br /&gt;&lt;br /&gt;Please also see these related posts...&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;T&lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses"&gt;he impact of Read-only mode on Sage 300 AP Module upon the expiration of the Subscription Licenses&lt;/a&gt;.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---ar-module"&gt;The impact of Read-only mode on Sage 300 AR Module upon the expiration of the Subscription Licenses.&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a title="The impact of Read-only mode on Sage 300 Admin Services upon the expiration of the Subscription Licenses" href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---admin-services"&gt;The impact of Read-only mode on Sage 300 Admin Services upon the expiration of the Subscription Licenses&lt;br /&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-common-services-upon-the-expiration-of-the-subscription-licenses"&gt;The impact of Read-only mode on Sage 300 Common Services upon the expiration of the Subscription Licenses&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-upon-the-expiration-of-the-subscription-licenses---gl-module"&gt;The impact of Read-only mode on Sage 300 General Ledger upon the expiration of the Subscription Licenses&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/the-impact-of-read-only-mode-on-sage-300-intelligence-reporting-upon-the-expiration-of-the-subscription-licenses"&gt;The impact of Read-only mode on Sage 300 Intelligence Reporting upon the expiration of the Subscription Licenses.&lt;/a&gt;&lt;/li&gt;
&lt;li style="list-style-type:none;"&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19298&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>Error Code: -2147467259  - Unknown error 0x80040200 when printing reports in Sage 300</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/error-code--2147467259---unknown-error-0x80040200-when-printing-reports-in-sage-300</link><pubDate>Wed, 05 Jun 2024 00:26:20 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:5149b715-5094-4fb2-8ddf-1f1ef77b89b7</guid><dc:creator>Dawie Nel</dc:creator><slash:comments>4</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19260</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/error-code--2147467259---unknown-error-0x80040200-when-printing-reports-in-sage-300#comments</comments><description>&lt;p&gt;We recently had a case where a customer got the below error whenever they tried printing any reports.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/1362.Picture1.png" /&gt;&lt;/p&gt;
&lt;p&gt;Often when cases are first logged with support, not all the relevant detail is supplied and, as a result, the complete picture often only becomes clear after several interactions. So, to make this easier to read, I have summarised all the information gathered in the next paragraph.&lt;/p&gt;
&lt;p&gt;In this specific instance, the issue occurred on a new standalone instance of Sage 300 2022.0 i.e. with no PU installed and a local installation of SQL. The users were able to create Journal entries, Purchase orders, AR invoices, etc. but were getting the error when attempting to print any reports.&lt;/p&gt;
&lt;p&gt;The error is rather generic but usually related to a file such as a4wcrinterop.dll which has either not registered properly, or is not accessible, corrupt, missing, etc. indicating that something went wrong in the environment requiring a repair of the installation.&lt;/p&gt;
&lt;p&gt;The partner confirmed that they attempted a repair via Control Panel &amp;gt; Programs and Features which did not resolve the issue.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://communityhub.sage.com/resized-image/__size/640x480/__key/communityserver-blogs-components-weblogfiles/00-00-00-00-45/0724.Picture2.png" /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;The error typically occurs if the installation and/or repair didn&amp;rsquo;t complete successfully e.g. wasn&amp;rsquo;t done &amp;ldquo;as Administrator&amp;rdquo; with full elevated rights on the PC. We therefore suggested they reach out to the customer&amp;#39;s IT to ensure that all the Sage 300 folders and files are whitelisted to prevent any antivirus / malware solutions from&amp;nbsp;interfering, or even temporarily disable them, failing which, a complete uninstall and reinstall might be necessary.&lt;/p&gt;
&lt;p&gt;We also referred the partner to a &lt;a href="https://communityhub.sage.com/us/sage300/f/general-discussion/204592/error-code--2147467259"&gt;Sage Community Hub post&lt;/a&gt; listing a number of things to check / try which others have tried and has resolved similar issues for them.&lt;/p&gt;
&lt;p&gt;After some further troubleshooting, the partner confirmed that completely uninstalling and then re-installing SAGE 300 with full rights, as well as running RegAcc.exe to ensure all files were registered, resolved the issue. They believe IT had done the initial installation, which might not have completed successfully, thus causing the issue.&lt;/p&gt;
&lt;p&gt;This case raised a few thoughts, and I would appreciate adding your own to the comments below.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Whilst IT teams are generally very capable of installing software, it does not replace the knowledge and experience of a certified Sage 300 consultant. How do you, as a consultant, ensure installs are done correctly when IT insists on doing the install?&lt;/li&gt;
&lt;li&gt;How often are you as consultants hampered from doing these installs due to the IT team or businesses concerns regarding costs or security?&lt;/li&gt;
&lt;li&gt;Working with IT teams and 3&lt;sup&gt;rd&lt;/sup&gt; parties can sometimes be challenging, especially when needing to manage the ongoing relationship, navigating trust whilst wanting to get the customer up and running as efficiently as possible. So, when problems do occur, what strategies do you use to validate that the IT team has completed the troubleshooting steps correctly?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A lesson learnt from a support perspective is that one cannot assume that the consultant raising the issue, was in fact the one doing the install or accessing the system to troubleshoot. Any feedback to these questions in the comments will help us support you in such situations, and hopefully anyone else reading this faced with a similar scenario as well.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19260&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>How LanPaks work with 3rd Party Integrations</title><link>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/how-lanpaks-work-with-3rd-party-integrations</link><pubDate>Wed, 10 Apr 2024 02:11:00 GMT</pubDate><guid isPermaLink="false">88fdc35a-04e2-45c9-a30d-9164df73f18c:d2622be5-32e8-4e8a-94a5-f1d055075152</guid><dc:creator>Santiago Gonzalez Perez</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/rsscomments?WeblogPostID=19220</wfw:commentRss><comments>https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/posts/how-lanpaks-work-with-3rd-party-integrations#comments</comments><description>&lt;p&gt;We recently were requested on some clarification on how LanPaks are consummed for Sage 300 integrations with 3rd parties.&lt;/p&gt;
&lt;p&gt;Where the 3rd party was advising the client that Sage had changed our Lanpak policies so therefore the integration would no longer work with the lanpak count that they originally had. This occurred after they upgraded the environment from Sage 300 2019 to 2024.&lt;/p&gt;
&lt;p&gt;They believed that they could no longer reserve LanPaks and we had changed our system behaviour also. The truth is that LanPaks have always remained the same and reserving LanPaks are still to this day a working function in all of our current supported versions of Sage 300.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We did some more digging as a team and found that what the 3rd Party was most likely using in the 2019 version of Sage 300 an Integration Access Pack (IAP).&lt;/p&gt;
&lt;p&gt;Sage discontinued this integration in version 2022. &lt;a href="https://help.sage300.com/en-us/2022/classic/Content/ReleaseDocs/ReleaseNotes.htm"&gt;Here are our release notes.&amp;nbsp;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Additionally that is when we started providing the ability to &amp;quot;Reserve LanPaks&amp;quot; giving 3rd party applications the right to be flagged as a designated user so they can always have access to Sage 300.&lt;/p&gt;
&lt;p&gt;So just wanted to write this blog as a reminder as sometimes it is hard to find these notices when they occurred in the past.&lt;/p&gt;
&lt;p&gt;The way Sage 300 LanPak&amp;rsquo;s are consumed has always been the same with the last change being the discontinuation of the IAP licenses as well as the introduction of an option to reserve a LanPak (subscription only feature).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://communityhub.sage.com/aggbug?PostID=19220&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/sage%2b300">sage 300</category><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/lanpaks">lanpaks</category><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/Integration">Integration</category><category domain="https://communityhub.sage.com/us/sage300/b/sage_300_erp_supporthub/archive/tags/3rd%2bparty%2bintegration">3rd party integration</category></item></channel></rss>