Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: SMMSS_SQLJOBS - Message class for SMSS_SQLJOBS
Message number: 004
Message text: Not running on MSSQL!
System databse platform is not SQL Server.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The report or function is not possible to execute in non-mssql server
system.
Error message extract from SAP system. Copyright SAP SE.
SMMSS_SQLJOBS004
- Not running on MSSQL! ?The SAP error message SMMSS_SQLJOBS004 typically indicates that a scheduled SQL job is not running on Microsoft SQL Server (MSSQL). This error can arise due to various reasons, and understanding the cause is essential for troubleshooting and resolving the issue.
Possible Causes:
- SQL Server Agent Not Running: The SQL Server Agent, which is responsible for executing scheduled jobs, may not be running.
- Job Disabled: The specific job may be disabled in SQL Server.
- Permissions Issues: The user account under which the job is running may not have the necessary permissions to execute the job.
- Job Schedule Issues: The job may not be scheduled correctly or may have been missed due to a configuration issue.
- Database Connectivity Issues: There may be connectivity issues between SAP and the SQL Server database.
- Resource Constraints: The SQL Server may be under heavy load or experiencing resource constraints, preventing the job from executing.
Solutions:
Check SQL Server Agent:
- Ensure that the SQL Server Agent service is running. You can check this in SQL Server Management Studio (SSMS) under the "SQL Server Agent" node.
Verify Job Status:
- In SSMS, navigate to SQL Server Agent > Jobs, and check the status of the job in question. Ensure it is enabled and not disabled.
Review Job Permissions:
- Ensure that the account running the job has the necessary permissions to execute the job and access the required resources.
Check Job Schedule:
- Review the job's schedule to ensure it is set up correctly. Make sure the job is scheduled to run at the expected times.
Examine Logs:
- Check the SQL Server Agent job history and logs for any error messages or warnings that could provide more context on why the job is not running.
Test Connectivity:
- Ensure that SAP can connect to the SQL Server database without issues. You can test this by running a simple query from SAP to the database.
Monitor Resource Usage:
- Check the SQL Server performance metrics to see if there are any resource constraints (CPU, memory, disk I/O) that could be affecting job execution.
Restart SQL Server Agent:
- If all else fails, consider restarting the SQL Server Agent service to see if that resolves the issue.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
SMMSS_SQLJOBS003
Schema not found!
What causes this issue? Schema not found.System Response The system issues an error message and will not allow you to continue with this transaction...
SMMSS_SQLJOBS002
No DB access!
What causes this issue? No database accessSystem Response The system issues an error message and will not allow you to continue with this transactio...
SMMSS_SQLJOBS005
DB not found!
What causes this issue? Database not found.System Response The system issues an error message and will not allow you to continue with this transacti...
SMMSS_SQLJOBS006
Error unknown!
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.