LVS Troubleshooting
©2011 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
TABLE OF CONTENT
INSTALLATION ... 3
No SQL Instance found ... 3
Server reboots after LVS installs ... 3
LVS Service does not start after update ... 3
RUNTIME ... 4
LVS Report Viewer HTTP error ... 4
LVS not generating reports ... 4
LVS can not login with “sa” account ... 4
LVS TROUBLESHOOTING 3 INSTALLATION No SQL Instance found Symptom Check During installation a message is displayed stating that no SQL was found.
• Connectivity with SQL.
• That the SQL version meets the minimum required.
Good performance of LVS depends on SQL connectivity and network performance. If any of these configurations does not meet the minimum required or the expected connectivity is not met, LVS will not install or run in the installation server.
Server reboots after LVS installs
Symptom Check
After LVS installation, the server restarts over and over again.
(For version 2.0)
• Start server in Safe Mode. • Change LVS start type to manual.
• Check .NET version (3.0) and repair as necessary. • Restart the server.
• Change LVS start type to automatic
• Check LVS version (the main issue was corrected in version 2.1)
• Check Server performance during start up.
When the server is restarting LVS connects to the SQL server. If the SQL server service is not available it will wait for it to start for a few seconds and retry. If the procedure fails recurrently, Windows restarts the server to correct the problem. If the above checks fail to solve the problem, you must check the state of SQL service and why it’s taking so much to start. Use the Windows event log to check the problem.
LVS Service does not start after update
Symptom Check
After updating to version 2.1, LVS service fails to start.
• Check LVS folder for the following files: ReportClasses.xml, ServerList.xml,
SAP.LVService.exe and SAP.LVService.exe.config. If one of the files is missing use a registry cleaning tool and reinstall LVS.
• Check .NET version (3.0) and repair as necessary. • Check the Windows Log Viewer for startup errors.
RUNTIME
LVS Report Viewer HTTP error
Symptom Check
When loading or trying to view a report, the LVS Report Viewer shows an HTTP error (with or without a number)
• Check that the LVS service is running.
• Check that the address in the LVS Report viewer is correct. • Download the latest version of Adobe AIR.
• Check the firewall so that the port used in the viewer is opened.
LVS Report Viewer is a light client that calls a webservice in the LVS server to get the information of the database. If the port or the service is unavailable, or if the address of the service is wrong, the LVS viewer will show an HTTP error. To check the address of the webservice you can open the SAP.LVService.exe.config file and search for the node <baseAddresses>, inside the node you will find and <add> node with the address of the webservice.
LVS not generating reports
Symptom Check
When you query any of the reports, they all show empty
• Check that the LVS service is running. • Check the Windows Event Log for LVS errors.
If you are not getting any results from the LVS report viewer is very probable that you will find an error on the Windows event log that explains the problem. If after checking the event log for error you don’t find any messages regarding the LVS service, uninstall the application (be sure to delete all the files present in the installation folder), clear the registry and install it again. Remember to backup the LVS DB before doing this procedure.
LVS can not login with “sa” account
Symptom Check
When you check the Windows log there is an error saying that the service can not login in with the sa user
• Test the sa password for changes.
LVS TROUBLESHOOTING
5
LVS Add-On stops working unexpectedly
Symptom Check
After working for some time in SAP Business One windows you get an error stating that the LVS Add-On has stopped working.
• Test client connectivity performance to the LVS server. • Check local firewall policies and correct accordingly.
• Change the receive event order of the Add-On’s so that LVS is the first one in the list. • Empty the Windows temp directory
LVS Add-On errors are related in most of the cases to connectivity to the server. If the communication’s port, network or response time of the client is not adequate, the LVS Add-On can stop working. As a security
measure, LVS Add-On stores the information locally in the Windows temp directory so that it can send it later. If the client can’t send the information for a very long period of time, and then the connection is reestablished, the client might crash generating the Add-On error. Empting the Windows temp folder and guaranteeing
