12 Replies Latest reply on Sep 8, 2008 3:45 PM by Mike Colombini

    Load times for B1 on workstations

    Henrik Lyder


      Our install of Business One experienced a serious slow down starting about 3 weeks ago. Everyone in my company started to complain over the suddenly increased time it takes B1 to load on their local workstations. We upgraded to B1 2007 but no help there. We had a network consultant look at our installation and after upgrading to gigabit networking he still found no evidence that could explain the slow load times. Our install is using a Win2003 SQL server, each workstation (XP-Pro) has B1 installed on its local drive, we are using B1 with the usability package. When loading B1 directly on the server the loadtimes are lower (not impressively so, but still), only the usability package continues to be slow.






      Any thoughts?






      Henrik Lyder



      Bentley Instruments



        • 1. Re: Load times for B1 on workstations
          Anthony Flores


          How Many Add-ons do you have running? We had this problem when we upgraded. To diagnoses the problem we de-activated the add-ons, started B1 and found it to be ok. Then we started each add-on one by one with the B1 and found which one that was causing the problem. We also updated our workstations to Service Pack 3. I didn't think that was the problem but wanted to be sure we had all the latest  updates.









          • 2. Re: Load times for B1 on workstations
            Henrik Lyder


            I only have the Usability package installed, the load problem is most evident in the time it takes from entering the username/password till the main menu appears. I think the add-on's load after this point.



            Which add-on where causing trouble for you?









            • 3. Re: Load times for B1 on workstations
              Anthony Flores


              There was a problem with a custom add-on. I checked and we also upgraded to SQL 2005.  I was reading over the first post again and you might have some configuration problems with the SQL, especially if the program is slow on the source server. Is the SAP on a dedicated server etc?



              Anthony... Compliance Poster Company... 800-817-7678



              • 4. Re: Load times for B1 on workstations
                Henrik Lyder


                SQL 2005 on a dedicated Win2003R2 server









                • 5. Re: Load times for B1 on workstations
                  Mike Grant


                  I agree, B1 load times are slow (as are exits from B1) and Add-Ons take even more time (we have 5, but not all are used by each person).  But our biggest problem since going live with 2007A July 1st is how long it takes to view/print our Crystal Reports (overridden forms and new reports) through the "Report One" add-on.  Some workstations (e.g.,2.5 GHz CPU, 512 MB mem) take 3-4 mins to view/print a report that takes me 30-40 seconds (1.6 GHz CPU, 2 GB mem).  So we bought $1000 worth of memory upgrades and that only improved things about 25-33%. That 2.5 GHz workstation with 2 GB of mem now view/prints in 3 minutes rather than 4.



                  We thought memory would take care of it, but obviously not, and cannot figure it out.  Anyone with some idea(s)?






                  • 6. Re: Load times for B1 on workstations
                    Sharon Chuang





                    My company has this program for 2 years. The thing you can try is create a new user in B1 to see any difference. If the new user is faster, you can check the message window. If there are a lot messages, it takes a lot time to load B1 before system loads any add on. Add on is another factor for slow performance(Another long story....). Anyway, try to clean the message from alert window, it won't hurt the system and it did improve when you log in to B1 according to my experience. Hope it help.









                    • 7. Re: Load times for B1 on workstations
                      Henrik Lyder


                      Hi Sharon



                      I have found a solution which involved running the license server on a server different from the SQL server (Dual-Core 2.3GHz Win2003). We loaded it onto an old  file server (PIII,1130MHz,Win2000). After this the loading times went back to normal. I don't know why this made the difference - I only know the effect.



                      The Add-On system in a continued source of slow-down's. Let's hope that the programmer at SAP has come of his/her sabbatical and is working on this.






                      • 8. Re: Load times for B1 on workstations
                        Dean Garrison





                        I am interested in knowing if there was any SAP related material describing your solution.  Sounds straight forward and we are going to attempt the same thing here, just looking for any data you might have.









                        • 9. Re: Load times for B1 on workstations
                          Henrik Lyder


                          Hi Dean



                          The solution came about after I had been giving our SAP partner some grief, they reported onsite to fix the problem and refered to this particular solution as having been suggested by SAP. It was never clear why this had the desired effect.



                          Sorry that I can not be of more help









                          • 10. Re: Load times for B1 on workstations
                            Chris Strahl








                            Often I've found that the longer load times are assocaited with problems blocking the port to the license server.  Depending on the server address that you're using (i.e. pointing to the host IP, the fully qualified domain name, or the internal domain name) you can create some issues associated with port 30000 (the license server port).  We've almost always found that these are server configuration or firewall configuration issues, but they're really hard to pin down.



                            Additionally, many clients have reported a slowdown in the login screen/choose company screen related to not having their databases refreshed.  SAP builds a connection to the SQL server based upon either SQL authentication or Windows Authentication.  Regardless, it seems to be doing some sort of check to see if all the databases are "alive" every time the login screen loads.  This may be an issue with authentication, but it sometimes it helps to refresh the database list and detach or remove any additional databases that may be present and unused.






                            Just a possibility.









                            • 11. Re: Load times for B1 on workstations
                              dan love


                              One thing to look at when logon times get slower and slower in SAP Business One is your Business One inbox.   Especially if the logon takes longer before the add-ons are loaded.



                              If you are using Alerts in Business One then it is possible that the OAIB and OALR tables are growing larger and larger if your users are not deleting these Alert messages from their Inbox.   The OAIB table stores the messages in the inbox and are keyed by alert and user-id. The OALR table has a record for each time a alert is fired in Business One and are keyed by Alert ID.



                              If you have an Alert that is triggered (conditions are met) and that Alert goes to 5 users, then there will be 5 new records in the OAIB table. If that Alert is set up to run every 5 mins and the 'Save History" check box is marked on the Alert, then you get 5 records each and every min to the OAIB table.  5x60x24 or 7,200 records a day. A reason why it is better not to check the Save History option on your alerts. 



                              If your users are checking their inbox and deleting these messages then the users OAIB, and possibly the OALR record are being deleted. If they don't check their inbox or don't delete them both tables continue to grow.   (the OALR record will not be deleted until each user message referencing that Alert ID is deleted).  So 1 user not deleting their Inbox alert messages then B1 will be keeping the OALR records.



                              So how does this impact the logon time....  



                              Well when you logon Business One one of the things it does after validating your user id and password is check the OAIB and OALR tables. With SQL Profiler I saw many SQL Select statements against the OALR table.  One statement for each record in the OALR table.....   In one client database I saw over 12,000 OAIB alert records for 1 user that had never been viewed or deleted. This 12,000 OAIB records meant 12,000 + OALR records which meant 12,000 individual SELECT statements against OALR at each and every sign on to Business One.   Since the user had never been taught to check their inbox and the General Setting>Services option "Display inbox when new message arrives" was turned off they never new they were getting Alerts.   This was compounded by 3 other user with similar counts in OAIB and cumulative in OALR.   Also many of the Alerts were to "OLD USER IDs" (ones that users never logged on to anymore because they had left the company) but were still generating OAIB and keeping OALR records. Many Partners allways include Manager on a Alert list and this id may no longer be used on a regular basis or even have licenses assigned anymore.



                              So the remedy is to run this quick query to see if you have the problem.



                              SELECT count(T0.usersign), T1.u_name from OAIB T0 INNER JOIN OUSR T1 ON T0.usersign = T1.Internal_K  Group BY T0.usersign, T1.u_name



                              This should list a row fore each userid and how many records they have in the OAIB table.  If the counts are high then you should sign on to these users and delete their old Alert Messages from the inbox.   if you do this for all users then they OALR records should also be deleted. This should cut down the logon time if you have counts like this one user.



                              The other thing to consider going forward is to review who is getting these alerts (remove old users and those that don't need to be informed) Also make sure that you don't have the Save History option turned on if not really required.  Also deactivate the alerts if they are no longer valid or being used.



                              Hope this helps



                              Dan Love  SAP



                              • 12. Re: Load times for B1 on workstations
                                Mike Colombini


                                I ran into this problem today after I enebled a second network card in the machine. Here is SAP explanation.









                                SAP Business One client (not installed on the same machine as the




                                service) might take several minutes to log you on successfully due to a

                                delay in establishing a connection with the license server.



                                After logon, SAP Business One functions as expected.




                                is due to the fact that the server or PC on which the license server is

                                installed has more than one network card, or there is a dial-up &

                                VPN interface-configured server.



                                Note: This can happen when you install the license service on a machine with more than one network card ALREADY installed.




                                additional network cards on a single network card machine with a

                                license service already installed might not produce this issue.



                                Other terms



                                SAP Business One, slow, login, log-in, delay, license, server, NIC, VPN, connection.



                                Reason and Prerequisites



                                Application error.






                                This issue is a candidate to be resolved in a future release.



                                Until then, you can use one of the following workarounds:


                                1. Disable
                                       additional network cards in the Network Connections. Also make sure
                                       there is no dialup interface or VPN interface set up, and restart the
                                       server. Note that you can re-enable the additional network card after
                                       the restart. This will resolve the issue until the next restart.

                                2. Install the license server on a machine with a single network card.

                                3. Disable all network cards, restart the license server and then enable the network cards again.