# SyteLine error -30006: how to find the real cause > Source: https://netray.co/erp-help/syteline-error-30006-and-how-to-read-error-messages > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer The number in a SyteLine error such as -30006 is a wrapper code. The useful information is the text after it and the underlying exception from the app server or SQL Server. There is no dependable public catalog of these numbers, so the reliable fix is a repeatable method for reading the message, reproducing it and checking the server side. ## Kind error ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Error handling / Diagnostics ## Query syteline error -30006 ## Alternate Queries - syteline error message - syteline error codes list - csi error message details where to find ## Applies To SyteLine 9.x and CloudSuite Industrial 10.x (client and web) ## Steps ### Diagnose a numbered SyteLine error **Items:** - Do not search on the number alone. Copy the complete message text and any 'details' content the dialog offers. - Note the form, the action (save, delete, run, post), the user, the site and the timestamp. - Reproduce it as a different user and in a test environment. If it only fails for one user, suspect permissions or personalization. - Check the application's message or event logs on the app server for the same timestamp. - Check the Windows Event Viewer on the app server and IIS logs for the web client. - Check SQL Server for an error at that time: deadlock, timeout, constraint violation, or a failed stored procedure. - Identify whether a customization (custom IDO, form script, event handler, extension class) is in the call path by testing with it disabled in a test tenant. - Search Infor Support with the full text plus the version and patch level. Open a case with the logs attached if it persists. ## Sections ### What the number does and does not tell you **Body:** Negative numbers in SyteLine and the Mongoose framework usually come from the framework layer reporting that a call failed. The same code can surface for different root causes, because the real error is nested inside it. I could not confirm a single documented meaning for -30006, so treat any forum claim that it always means one thing with suspicion. What does stay stable is the structure: a framework error, wrapping an IDO or stored procedure error, which wraps a SQL Server or .NET exception. Your job is to peel back to the innermost message. ### Where the detail lives **Body:** Start on the client: the error dialog usually has a details or more-information option with the stack and inner message. Capture a screenshot or copy the text. Next, the server side. The app server (IIS and the IDO runtime) writes to the Windows Event Log and to its own message logging, and background tasks write to the task history. SQL Server holds the final word on data errors, so check its error log and, for intermittent problems, an Extended Events session or Profiler trace filtered to the user and time. **Code:** - -- Find recent deadlock or error events (SQL Server 2016+) EXEC xp_readerrorlog 0, 1, N'error'; -- Then correlate the timestamp with the failing user action ### Common categories behind numbered errors **Body:** In practice most framework errors fall into a short list: a data rule violated by a custom stored procedure; a timeout between the app server and SQL; a permission or authorization failure on an IDO method; a missing or mismatched customization after an upgrade; or a session problem. Classifying the error into one of these cuts the search in half. Upgrades are a frequent trigger. If a message appeared right after a patch, compare customizations promoted to the new version and check that custom IDO assemblies were rebuilt for it. ## Pitfalls - Googling only the number and applying a fix meant for a different root cause. - Fixing the client when the failure is in a stored procedure or SQL timeout. - Testing as an administrator, which hides permission-based failures. - Ignoring customizations in the call path. - Not recording the timestamp, which makes server logs hard to match. ## Ai Angle A SyteLine-grounded assistant (SyteRay) can take the full error text, find which forms, IDOs and custom methods are involved from your metadata, pull recent log lines and SQL events at the timestamp, and propose the likely category with the evidence. On-prem, the logs and metadata never leave your environment. It diagnoses; applying fixes remains with your admin. ## Faq ### What does SyteLine error -30006 mean? **Answer:** It is a wrapper code, and the underlying cause varies. The text and nested exception that accompany it identify the real issue. Collect the full message, the form and action, then check app server and SQL logs for the same time. ### Is there an official list of SyteLine error codes? **Answer:** Not one that reliably maps each number to a single cause. Infor Support documentation and knowledge base articles cover many messages by text. Searching on the full message plus your version works better than searching on the number. ### Why does the error only happen for one user? **Answer:** Look at permissions, user-level personalization, and session or license state. Reproduce it as another user. If the other user is fine, compare their authorizations and form settings. ### When should I open an Infor support case? **Answer:** When you have ruled out customizations and data, and can reproduce the issue in a test environment. Attach the full message, version and patch level, timestamps and the relevant server and SQL log extracts. ## Search terms syteline error -30006, syteline error message, syteline error codes, csi error details, mongoose framework error, syteline troubleshooting errors, syteline ido error, syteline event log --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json