Distribution Archives

Elastic Computing Revolutionizes Business Dynamics

by EstesCloud | Sep 26, 2023 | Backup, Business Consulting, Business Direction, Cloud, Disaster Recovery, Distribution, ERP, Managed IT Services, Prophet 21, Security, SYSPRO

Cloud Resources are Changing the Manufacturing and Distribution Industry Landscapes

In the world of cloud options for businesses, elastic computing refers to the ability to dynamically scale computing resources up or down based on demand, without the need for significant manual intervention. It involves the use of cloud computing and virtualization technologies to provide flexibility and cost-efficiency in managing IT infrastructure. This allows for greater flexibility and scalability, as resources can be easily scaled up or down based on dynamic business needs. Cloud computing also eliminates the need for organizations to invest in and maintain their own physical infrastructure, such as on-site servers, reducing costs and increasing efficiency.

What is Virtualization?

Virtualization, on the other hand, involves creating a virtual version of a device or resource, such as a server, operating system, or storage device. This virtualization technology allows multiple virtual instances to run on a single physical machine, effectively maximizing the utilization of hardware resources. By consolidating multiple virtual machines onto a single physical server, organizations can reduce the number of physical servers required, leading to cost savings in terms of hardware, power, and cooling.

Bringing Cloud and Virtualization Together

When combined, cloud computing and virtualization technologies offer numerous benefits for managing IT infrastructure. Firstly, they provide flexibility in terms of resource allocation. With cloud computing, organizations can easily scale up or down their computing resources based on their needs, ensuring that they have the right amount of resources at any given time. Virtualization allows for the efficient utilization of hardware resources, enabling organizations to make the most of their existing infrastructure.

Pay-As-You-Go, Quick-To-Market Technologies

At the end of the day, new cloud-based technologies offer cost savings throughout the entire business ecosystem. By leveraging cloud computing, organizations can avoid the upfront costs associated with purchasing and maintaining physical infrastructure. Instead, they can pay for the resources they actually use on a pay-as-you-go basis.

Virtualization further reduces costs by allowing organizations to consolidate their hardware resources, reducing the number of physical servers required and the associated costs of power, cooling, and maintenance.

Additionally, cloud computing and virtualization technologies enhance the agility and scalability of IT infrastructure. With cloud computing, organizations can quickly provision and deploy resources, allowing for faster time-to-market for new applications and services. Virtualization enables organizations to easily scale their infrastructure up or down based on demand, ensuring that they can meet changing business needs without disruption.

Furthermore, these technologies improve the reliability and availability of IT infrastructure. Cloud computing providers typically offer robust infrastructure with built-in redundancy and failover mechanisms, ensuring high availability of services.

Virtualization also enhances reliability by isolating virtual machines from each other, preventing issues in one virtual machine from affecting others.

The use of cloud computing and virtualization technologies in managing IT infrastructure provides organizations with flexibility, cost-efficiency, agility, scalability, reliability, and availability. By leveraging these technologies, organizations can optimize their resource utilization, reduce costs, and improve their overall IT operations. Here are the top 10 benefits of elastic computing for manufacturing and distribution businesses:

Scalability

Elastic computing allows businesses to easily scale their IT infrastructure to accommodate fluctuating demand, ensuring that resources are available when needed without over-provisioning.

Cost Efficiency

By scaling resources up or down as required, businesses can optimize their IT costs, paying only for the computing power they actually use, reducing overall expenses.

Resource Optimization

It enables efficient use of computing resources, avoiding underutilization during periods of low demand and preventing resource bottlenecks during peak periods.

Improved Performance

Elasticity ensures that applications and systems can maintain consistent performance levels even during traffic spikes or increased workloads.

Flexibility

Businesses can quickly adapt to changing market conditions or unexpected events, such as seasonal variations in demand or unforeseen disruptions by adjusting computing resources in real time.

Reduced Downtime

Elastic computing minimizes the risk of system failures or downtime due to resource constraints, as additional resources can be provisioned automatically in response to increased load.

Enhanced Disaster Recovery

Elastic computing can support robust disaster recovery and backup solutions, enabling businesses to replicate their systems across multiple locations or cloud regions for data redundancy and resilience.

Global Reach

Businesses can leverage cloud providers’ global data center networks to expand their operations into new regions and markets without the need for physical infrastructure investments.

Resource Isolation

Elastic computing can provide resource isolation and security, ensuring that applications and data remain protected even when sharing cloud infrastructure with other users.

Agility and Innovation

With the ability to rapidly provision and experiment with new resources and technologies, businesses can innovate more quickly and bring new products or services to market faster.

The Value in Cloud Elasticity

In manufacturing and distribution, elastic computing is particularly valuable because it allows companies to handle seasonal demand fluctuations, respond to supply chain disruptions, and efficiently manage their IT costs. In today’s fast-paced and ever-changing marketplace, businesses need to be agile in order to stay competitive. This means being able to quickly adapt to new trends, technologies, and customer demands. Agility allows companies to respond swiftly to market changes, seize new opportunities, and stay ahead of the competition.

However, agility alone is not enough. Businesses also need to ensure the reliability and performance of their critical systems. These systems are the backbone of the organization, supporting key operations and processes. Any downtime or performance issues can have severe consequences, such as lost revenue, damaged reputation, and dissatisfied customers.

By combining agility with reliability and performance, businesses can achieve a winning formula. They can swiftly respond to market changes while maintaining the stability and efficiency of their critical systems. This requires a careful balance between innovation and stability, as well as a robust infrastructure and effective risk management strategies.

Agility enables businesses to quickly adapt their strategies, products, and services to meet changing customer needs and preferences. It allows them to experiment, iterate, and pivot as necessary, without being tied down by rigid processes or outdated technologies. This flexibility is crucial in a dynamic marketplace where customer expectations are constantly evolving.

On the other hand, reliability and performance ensure that businesses can deliver on their promises consistently. Customers expect products and services to work flawlessly, without any disruptions or delays. Critical systems, such as e-commerce platforms, supply chain management systems, or customer support systems, need to be highly available, scalable, and efficient. This requires robust infrastructure, rigorous testing, and proactive monitoring to identify and address any issues before they impact the business.

Why Manufacturers and Distributors are Choosing EstesCloud

Businesses need both agility, reliability, and performance to thrive in today’s dynamic manufacturing and distribution industry landscape. Agility allows companies to adapt and innovate, while reliability and performance ensure that their critical systems can support their operations effectively. By striking the right balance between these two factors, businesses can remain competitive, deliver exceptional customer experiences, and achieve long-term success.

Ready to move your business to the cloud? In the cloud and ready for a better cloud environment?

Get Help With IT Today

SYSPRO UI & Layout Problem Solving

by EstesCloud | Sep 26, 2023 | Cloud, Distribution, ERP, ERP Consulting, ERP Implementation, Manufacturing Innovation, SYSPRO

Troubleshooting user interfaces and personal layout issues in SYSPRO

Throughout the various releases and versions of SYSPRO, user interfaces and layout issues are common. Despite several significant changes to the methods of how SYSPRO stores and saves user settings, these issues are still frequently occurring even in the latest SYSPRO releases. User changes not being saved, pane locations not sticking to where they were configured, and SYSPRO windows appearing off screen are a few of these types of problems. To effectively combat these issues from a SYSPRO administrator perspective, it is important to understand how SYSPRO handles files relating to user settings and program layouts. All these issues begin and end within a folder called “Settings”.

SYSPRO stores personal operator settings in text files within a folder found both locally on the client machine and on the SYSPRO application server. The folder is called “Settings” and can be found in the following locations:

Client machine – “C:\SYSPROClient\Base\Settings”
Application Server – “C:\SYSPRO\Base\Settings”

When a user closes out of SYSPRO on their client machine, any changes made to their layouts or personal settings will be saved to this directory. The client machine syncs the files to the application server and overwrites any non-identical files for that user. The settings are stored on the application server to serve as a backup in case the user gets a new computer or signs in from another machine.

When the user signs in to SYSPRO again, the client machine compares the local setting files to the ones on the application server and restores any missing files or updates existing ones based on the modified date of the files.

As this back-and-forth process takes place, it is possible that settings files become corrupt due to various reasons such as a disconnect between the client and the app server. Thankfully, it is almost always the local files on the client machine that are corrupt and not the ones on the application server. What this means is that it is possible to clear and “refresh” a user’s settings by renaming the client-machine’s “Settings” folder (ex, “Settings_old”). By doing so, SYSPRO notices that the folder is no longer there and recreates a new “Settings” folder based on the files stored on the application server. This is an effective solution to a variety of issues that an operator may experience in a SYSPRO client environment.

Instead of renaming the entire “Settings” folder, it is a good practice to target specific settings files first. For instance, if it relates to an issue within Sales Order Entry (IMP040), you can search the “Settings” folder for IMP040 specific files and try removing those first. When the user signs-in to SYSPRO, the app server files will be restored to the client as they are detected as missing. If this doesn’t resolve the issue, you can then attempt the full renaming of the “Settings” folder.

If you choose to target any specific files, be sure to back them up and restore them to the folder if removing them did not resolve the issue.

Troubleshooting application server file corruption

If corruption is suspected with the application server files, then there is little that can be done in terms of restoring or recovering the user’s settings. As explained above, the app server replaces the files on the client machine in the event of any discrepancies between the user’s settings files. If they are corrupt on the app server, they will transfer and overwrite the local files and remain corrupt. In this case, we recommend seeking support from SYSPRO’s support team itself as modifying the “Settings” folder on the application server can result in potential loss of layouts and user settings for all operators in your SYSPRO environment.

Also, note that SYSPRO is and have actively been updating the amount of information stored on the application server and in the SQL database with each new SYSPRO release. Prior to SYSPRO 8 2021 R1, many types of settings are only stored locally and cannot be restored by the app server. You can try this suggested fix if you are dealing with an older SYSPRO release, however, there is no guarantee that the app server has a copy to restore so the user’s layout may reset to default.

If this fix does not resolve the user’s problem, you can try to either “Repair” or uninstall and reinstall the SYSPRO client on the user’s machine itself. This may help resolve corruption within direct program files unrelated to personal user files. If you renamed the “Settings” folder and it did not resolve the problem, be sure to restore the prior settings folder by renaming the original folder back to “Settings”.

Looking for more help with SYSPRO UI & other ERP system or IT issues? Schedule a free one-on-one consulting session with a SYSPRO ERP or IT consultant today!

LET'S TALK SYSPRO ERP

SYSPRO Data Integrity: A Guide to Balance Functions

by EstesCloud | Sep 19, 2023 | Business Consulting, Distribution, ERP, ERP Consulting, ERP Implementation, Hosting, Managed IT Services, Software, SYSPRO

How to Ensure Data Integrity Within SYSPRO – Balance Functions Explained

Ensuring data integrity is a top priority for any software product, especially for an ERP such as SYSPRO. As users go about performing their daily activities, various problems can arise, even with the most mature ERP systems. The most common issues seen within SYSPRO that can lead to data instability are users being disconnected, programs freezing up, or business objects unexpectedly stopping in the middle of processing. With tens (or potentially hundreds) of daily active users, it is imperative for your business that the data within SYSPRO stays consistent. So how does SYSPRO combat data integrity problems and maintain the overall stability of its data? The answer is SYSPRO balance functions!

A balance function in SYSPRO is a detailed process used to correct and adjust database information if discrepancies are detected. They are built in to SYSPRO’s Period-End programs and are supposed to be run prior to posting GL entries or performing Month-End/Year-End tasks. SYSPRO’s balance functions can help “balance” a module by comparing user transaction data to its own control totals and correcting any noticed discrepancies. Some examples of these discrepancies that it can correct include:

GL journal entries that have not been properly completed or are still marked with “in-process” flags if they were abandoned. Users unexpectedly disconnecting from the system can be a cause of this.
Failed inventory transactions. Minor hiccups from bugs or networking issues during inventory transactions can result in inaccurate inventory counts. For example, a stock code may display as having available quantity on-hand but an attempt to issue or release the quantity results in errors.
Specific key documents being locked down by users for maintenance that fail to be released once complete. Again, a potential result of unexpected user disconnects or program errors. These are commonly encountered within sales/purchase order entry and customer/supplier setups programs.

Scheduling SYSPRO Data Integrity Tasks

While most SYSPRO environments generally only run these balance functions during their period-end tasks, it is strongly recommended to schedule balance functions to run regularly. Sites with heavy user activity (including custom business object activity) may want to run balance functions overnight several days throughout the week. The result of this will be an improved and overall smoother SYSPRO experience for all users.

Balance functions are not found separately within their own respective program. Instead, they are usually part of and located within period-end programs. The naming convention of some of these programs may not be clear and it is not easy to identify all of them. As such, here is a full list of the programs within SYSPRO that contain or can perform the functionality of a “balance function”:

AP Period End
AR Period End
AR Bank Deposit Slip
Cash Book Period End
Assets Period End
Inventory Period End
Sales Order Purge
Purchase Order Purge
GRN Purge
Sales Analysis Update

It is imperative to understand that some of these programs contain critical data-altering functionality within SYSPRO relating to period-end module closures or purging of data. You should tread with caution when accessing these programs and ensure you only have “Balance” selected. NOT any unwanted options pertaining to period-end and/or data purge functionality!

Some of the above-listed programs may have an option called “Reset lowest unprocessed journal”. As it is not always checked by default, it is recommended to enable this option prior to executing a balance function. It performs an additional data-stability feature intended to fix GL journal issues.

SYSPRO Data Integrity Balance Functions AR Period Example

SYSPRO environments that are not familiar with the power of balance functions can (and will) encounter unwanted issues and potentially unstable data problems. Knowing how to utilize, execute, and schedule balance functions is key to ensuring your SYSPRO environment’s data remains both stable and trouble-free.

Ready to discover how an EstesGroup ERP consultant tackles data integrity challenges & ensures your company’s success? Chat with us now or sign up for one of our newsletters to get SYSPRO case studies, white papers, customer testimonials & more!

How to Use SYSPRO Form Actions

by EstesCloud | Sep 16, 2023 | Distribution, ERP, ERP Consulting, ERP Implementation, ERP Selection, Hosting, Managed IT Services, SYSPRO

SYSPRO Customization Station

When it comes to Enterprise Resource Planning (ERP), SYSPRO is the ultimate software choice for manufacturing and distribution companies in search of flexibility and customization. EstesGroup has an expert understanding of the SYSPRO User Interface, and our team of IT professionals is ready to help your company understand your applications and your functionality. Form actions are an important aspect of the SYSPRO User Interface that are very beneficial to your users. By understanding SYSPRO form actions, specifically how to add, remove, and customize them, users will be able to realize the full benefits of your ERP application.

What is a SYSPRO Form Action?

The SYSPRO User Interface includes implemental form actions that facilitate easier display and data entry in SYSPRO applications for its users. Form actions are “user-definable hyperlinks”, and users can find these form actions in the Action Panel at the bottom of the form.

In terms of functionality, users can configure form actions to identify a SYSPRO program and advance its parameters. Form actions are also important in initiating and advancing VBScript events.

The SYSPRO User Interface has great flexibility in allowing many form actions for each form as well as customized combinations of types. Users can display or hide form actions on a form, and hiding a form action does not negate the form action’s VBScript functionality.

Form Action Benefits for Users

SYSPRO’s User Interface is truly flexible and customizable, especially when your ERP system is deployed in EstesGroup’s Estes Cloud Hosting (ECHO) environment, positioned in our top-tier, highly secure data center. Form actions benefit SYSPRO users in many important ways including:

Adding program shortcuts
Removing program fields
Customizing program fields
Easy display and data entry
Quicker data entry
Data entry verification

How SYSPRO Users Can Utilize Form Actions

How to Add

Once users begin to interact with SYSPRO, understanding how to add a program shortcut will help streamline the experience and save time. In order to add a program shortcut on the same screen, users should follow these basic steps:

Locate the SYSPRO screen where a shortcut is needed (e.g. stock codes).
Select the desired field property you would like to add a shortcut to, and click on “insert form action”.
Add the appropriate cross-reference.
Once the screen is closed, the shortcut is saved.
Open the field property and verify that the shortcut has been successfully added to the SYSPRO screen.

How to Remove

SYSPRO facilitates the easy removal of form actions if users would like to change or remove an improper shortcut. In order to remove a form action in a SYSPRO screen, users should follow these basic steps:

First, locate the SYSPRO screen where a form action removal is needed (e.g. stock codes).
Next, locate the form action on the SYSPRO screen.
Select “add cross-reference”.
A display box will appear. Select “yes” to confirm removal of the form action.
Once the screen is closed, the form action removal is saved.
Finally, visit the SYSPRO screen to verify that the cross-reference shortcut is no longer available.

Simplifying Your Business With ERP Customization

SYSPRO makes data entry, verification, and manipulation of form actions easy. Users will enjoy the benefits that the ERP system provides with its streamlined and time-saving processes regarding form actions, specifically adding and removing shortcuts.

Beyond this basic understanding of the SYSPRO User Interface and form actions, EstesGroup is available to help users understand these processes in even greater detail. EstesGroup’s ERP and IT professionals are available at any time of the day to assist users with their ERP software needs and questions.

TALK TO A SYSPRO ERP EXPERT NOW

Watch Our Happy Customers Discuss Their ERP Journeys

P21 Public Web Client Access – Who’s Your Proxy?

by Marshall Douglas | Apr 14, 2023 | Backup, Cloud, Distribution, Epicor, Managed IT Services, Prophet 21

ERP systems have traditionally had a functionality-accessibility problem: ERP systems were highly functional, but not especially accessible – they normally required desktop fat-client applications for access, and these were often hamstrung by local access requirements, making applications far from mobile.

As internet architectures became more and more robust, the possibility of web browser-based ERP became a reality, with new ERP vendors designing and building their software around the browser, and legacy vendors systems hastening to retrofit their existing ERP systems to accommodate the browser-based future.

But this introduced a new problem – one of accessibility vs security: the high levels of availability increased the possibility that threat actors could access a company’s ERP system remotely, and cause havoc to company data.

Most load balancers make it relatively easy to have an app safely deployed publicly. Normally, you run a reverse proxy server that passes traffic to your web app. This obfuscates the info for the destination of the web app and basically acts as a secure gateway to the internal resource. At EstesGroup, P21 Web UI is protected by MFA via a reverse proxy to the identity provider as well. However, administration of the Prophet 21 application introduces additional challenges. The P21 web login page contains a gear icon.

If a P21 user clicks the gear, they can access the Middleware server URL value, along with its port.

This introduces several complications:

It basically shows users a free shortcut around MFA. A clever user can copy and paste the Middleware URL and port into their browser and access the P21 application directly, avoiding the MFA.
The Middleware server URL and port are resolved on the P21 client side of the P21 application when logging in. This means, even though the Load Balancer can reverse proxy to the internal resource, it’s not going to be able to resolve the specific Middleware server URL on the P21 client side to complete the P21 login.

To get around these challenges, you might initially think to expose the Prophet 21 Middleware server to the internet and add a public DNS entry for it. But to directly expose P21 Middleware servers to the internet in that manner is a monumental risk. Another option is required.

To address the above issue, we do the following:

We create a middleware reverse proxy to direct traffic to the middleware servers.
We direct the P21 Web configurations to use the middleware proxy for its respective Middleware Server.
We then expose the reverse proxies to the internet, creating DNS records for each of them.

By exposing the Middleware server proxies to the internet through a public DNS instead of the middleware servers themselves, you add a line of defense to the servers, only passing that needed traffic and keeping P21 Middleware Servers from being directly internet-exposed.

Another advantage of reverse proxying is the ability to intercept direct-access attempts. Theoretically, one might try to plug in the Middleware proxy URLs publicly and get access to the P21 API or the P21 Web UI. The reverse proxy allows for the functionality to block certain endpoints, such as the API or web client. When a user sees the Middleware URL in the P21 login settings, if they try to get around MFA and plug that URL in, they get a lovely 403 page, keeping them out of the Middleware. Alternatively, you can also redirect them back to the Web UI home page.

While there are other solutions for increasing accessibility, such as accessing through a VPN, these can at times be unreliable. If you are a decentralized company, with remote employees all over the country, speeds over VPN can be less than ideal on many occasions. Obviously, there are certain risks to opening any resource to the internet. It’s important to consider the attack surface, and the associated risks. At EstesGroup, we isolate any resources open to the internet, and implement Antivirus, Firewalls, and Threat Protection for all endpoints. Along with that, oftentimes, Geofencing helps cut out a lot of noise on any resource open to the internet, to prevent overseas attackers using botnets.

Marshall Douglas, EstesGroup Systems Engineer

Have questions about Epicor P21 public web client access? Schedule a free consultation or ERP cloud solutions demo with the author now.

Epicor Prophet 21 Performance – Real-World Issues

by Brad Vandenbogaerde | Mar 8, 2023 | Cloud, Distribution, Epicor, Prophet 21, Software

Recently, I met with an Epicor Prophet 21 customer on a discovery call to review the issues they were encountering in relation to some ongoing P21 web UI slowdowns. ERP system performance is a common challenge across the ERP community, and in the Prophet 21 community, the subject of P21 performance is similarly of great importance. Coming out of the call, I thought I’d collect a few of the talking points and add a few additional P21 system performance considerations that can impact the speed and responsiveness of your Prophet 21 web UI.

Epicor Prophet 21 Performance Distribution Industry

Epicor Prophet 21 system performance can be a maze to navigate.

We had originally characterized the issue as a problem with the P21 API loading, and we began looking more broadly. As you might know, the Prophet 21 sits on top of Microsoft’s Internet Information Services web server platform, known colloquially as “IIS”. There are several things to consider if your P21 web server is slowing down throughout the day, and with an ERP system like P21, the issues actually affecting the performance of the Prophet 21 web interface may reside many layers below the P21 web server.

Background:

It might be helpful to initially review the composition and operation of websites. Websites are comprised of both static and dynamic pages. A static page is pre-defined on the web server and is ready to be served up. A dynamic page is generated at run time and may dynamically differ each time it is generated. In terms of HTML pages that comprise the P21 user interface, generally speaking, the P21 application pool can only respond to a certain number of requests at a time. If it is busy responding to requests for dynamic pages, then it may not have any threads left to serve the static pages. For this reason, a code problem on a dynamic page can create the illusion that the static pages are being served “slowly”. My point is, don’t rule out code or SQL. As an example, if you have 100 pages all hitting a database or API at the same time, and all 100 await a response, request 101 may be blocked until one of the first 100 requests completes.

Diagnosing the Degradation:

Beyond explicit issues like request load, there are plenty of things that you can do to help you diagnose performance problems with your Prophet 21 web application:

Load Profiles: What does your load profile look like normally? This makes a big difference – it may be that you always have an issue, but you can’t see the impact until your site receives load. You could try to test this (in staging) with something like JMeter.

Reviewing your logs: Does your application have logs? If not, you should consider adding some logging. If you already have logs, what do they say? Are there exceptions being thrown by your application? Is there something that is consistently failing?

IIS Logs: Enable IIS logs if you haven’t already. Reviewing your P21 IIS logs can help you see which requests are taking the longest. You can use something like Microsoft’s Log Parser to run SQL-like queries against your logs. You may even want to dump your logs into a SQL database if that makes your P21 logs easier to review. Once you know which pages are taking the longest, you can focus some of your attention on them.

Memory: How much memory is your application pool using? A memory leak is an obvious candidate but should be quite easy to see. Use Windows’ inbuilt Performance Monitor to track memory consumed by your application pool over the day and see if this increases as the day goes on.

SQL Performance: The performance of your P21 SQL database may be an underlying cause of poor Prophet 21 user interface performance. SQL server provides a series of query structures called Dynamic Management Views, or DMVs, that can provide details about server and database health and performance. These can be very helpful in diagnosing performance issues at this level. One common DMV, sys.dm_exec_requests, can help you understand query properties such as wait_type, wait_time, blocking_session_id and the total_elapsed_time.

P21 Application Pool Connections: Check how many connections your application pool has open – using something like Microsoft’s TCPView. Your application pool will try to re-use connections where possible, but you’ll probably see a lot of open connections to your application pool. One interesting thing you can see from this is how many connections you have open to your SQL database or any external APIs your application is using.

Use an Application Performance and Monitoring Tool: Performance monitoring tools, like AppDynamics, will be able to help pinpoint slow performing parts of your code. Unfortunately, there’s a little bit of a learning curve to be able to use these tools effectively, but they can be very powerful in helping to diagnose problems with your applications.

SQL Server AutoGrowth Property: Review the property in your SQL database pertaining to AutoGrowth. You may encounter issues if the following are occurring:

1. If the database is a super-busy database, transactionally speaking.

2. If AutoGrowth is enabled.

3. The AutoGrowth default is a smaller MB amount. This may cause random slowdowns on the database engine, which could impact the API application pool response time.

One thing to test would be to set that AutoGrowth size in MB to a very large number. That way, the AutoGrowth will only happen periodically.

Look for Memory Leaks: Once I had a customer experiencing IIS performance degradation issues with a custom web application we had built that was using asp.net and Crystal runtime integration. Ultimately, the issues with IIS and the web app related to memory leaks that were not obvious at all until we started doing some deep-dive testing. You will want to consider the possibility of internal memory leaks when building a support case against the application having performance-related issues that may or may not have been resolved in minor version changes. I know IIS also plays a part in this and how it manages internal garbage disposal with application pools, so this may be an area that you need to explore as well.

As you can see, Epicor Prophet 21 system performance can be a maze to navigate. To find your way through the P21 performance maze, there are many potential paths to take, and depending on the ultimate source of the problem, many might be dead ends. But in understanding the directions one might take in navigating the many potential Prophet 21 performance issues, P21 users can hopefully find themselves at the maze’s end – and moving on to bigger and better things.

Schedule Time With the Author, Brad Vandenbogaerde