The automation server can not create object error is a message that many people have encountered at one point or another. This article will help you understand what this message means and how to solve it.
This blog post will show you:
What the automation server can not create object error is, and why it occurs
How to fix the automation server can not create object error
The first step is to understand what the automation server can not create object error means. This message occurs when there’s a problem with permissions on the directory that contains your Fortinet configuration file, or you have reached the maximum number of licenses for Log and Event Management (LEM). Sometimes this error also points to an issue with non-English characters in a configuration file name.
To fix automation server can not create object errors, we recommend checking if any other files within the directories are older than your Fortinet config file by comparing their timestamp: If one has been modified more recently then it may be overwriting changes made to your fortinetconfig.xml without saving them back out again – so please make sure all files are being saved before you try to make any changes.
If this doesn’t fix the automation server can not create object error, please contact Fortinet Technical Support for assistance with your problem.
Automation Server Can Not Create Object is a common message and often indicate an issue with permissions on the directory that contains your Fortinet configuration file or access has reached maximum number of licenses for Log & Event Management (LEM). This article will walk through how to troubleshoot these issues so that you don’t have to contact Technical Support for assistance.
In the Windows directory, look at the file permissions and see if you can identify a problem with your Fortinet configuration folder or access has reached maximum number of licenses for LEM.
Administrator has permission denied
If you see Administrator has permission denied, make sure your administrator account is on the Local Administrators group. If not, add it to that group and try again.
Access Has Reached Maximum Number of Licenses for LEM
If you are using an automation server: Make sure all Fortinet sensors have been added in the automation server console. You can also contact technical support at [email protected] if you need assistance with troubleshooting this issue (please refer to article “Automation Server Cannot Create Object” below).
Incorrect Permissions Issue – Disabling Security Mode and Changing Owner Rights
This section will focus on how to correct permissions issues when security mode is disabled or incorrect owner rights exist for automation and management servers. The permissions issue can be solved by changing the owner rights of automation server folders or disabling security mode for automation server.
If you are using an automation server: Make sure all Fortinet sensors have been added in the automation server console. You can also contact technical support at [email protected] if you need assistance with troubleshooting this issue (please refer to article “Automation Server Cannot Create Object” below).
To fix incorrect permissions issues related to automation server:
Make sure to grant the automation server read/write permissions to all Fortinet sensors.
If that does not resolve the issue, then contact technical support for assistance (please refer to article “Automation Server Cannot Create Object” below).
If you are using a controller: You should make sure your configuration is correct and both your automation server and controllers have permission access rights in order for this connection to work correctly. When adding new devices into an automation controller, it will be necessary for them to create their own user account within FortiDB before they can authenticate with your automation system via LDAP or RADIUS. This user account must also be granted read/write permissions on any configured sensors that exist on the automation server.
This blog post provides information about how users can troubleshoot automation server can not create object issues.
Automation Server Cannot Create Object: Troubleshooting Guide for Errors
It is possible for an error to occur during the process of creating data objects in your automation sever, which may cause it to be unable to authenticate with a controller or log into LDAP/RADIUS servers properly. There are many reasons why this could happen and below we will explore some common causes and troubleshooting steps that you can take when trying to resolve these errors.
Make sure your configuration is correct on both the automation server as well as any controllers that communicate with it (Make sure they have permission access rights). When adding new devices into an automation controller, they will need their own user account and password. This will need to be populated on the automation server and in any other controllers that are communicating with it.
Check your automation server’s logs for detailed information about why this error occurred, what caused it, or if there is a way to resolve the issue. You can do this by executing ‘show log access’ from within an automation controller console: “show log access” (This command shows all system messages including those coming from administrative commands). If you’re unable to find anything useful in these logs, try running debug traceback which may provide additional details such as device names to investigate further into errors related specifically to authentication processes.
