Error 1064 when starting NintexRPACentral service

  • 25 October 2021
  • 5 replies


When starting NintexRPACentral service we get an "Error 1064" and the service could not be started.

Running the latest version, RPA Central 2.5.0.


Best answer by BGottsberger 25 October 2021, 23:48

View original

5 replies

Hello, thank you for contacting us. When the service fails to start, there should be a log file written in the RPACentral install location which will help us find the error. This will most likely be in the below directory:

C:Program Files (x86)NintexRPACentralRPACentralRPACentralStartupLogs.txt

Could you please attach the relevant log file here?

Level Date and Time Source Event ID Task Category
Error 10/25/2021 5:48:14 PM .NET Runtime 1026 None "Application: RPACentral.ServiceHost.exe
CoreCLR Version: 4.700.21.41101
.NET Core Version: 3.1.19
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Data.SqlClient.SqlException (0x80131904): Database 'RPACentralWeb' already exists. Choose a different database name.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite, String methodName)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.Execute(IRelationalConnection connection, DbCommandMethod executeMethod, IReadOnlyDictionary`2 parameterValues)
at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.ExecuteNonQuery(IRelationalConnection connection, IReadOnlyDictionary`2 parameterValues)
at Microsoft.EntityFrameworkCore.Migrations.MigrationCommand.ExecuteNonQuery(IRelationalConnection connection, IReadOnlyDictionary`2 parameterValues)
at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQuery(IEnumerable`1 migrationCommands, IRelationalConnection connection)
at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Create()
at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.Migrate(DatabaseFacade databaseFacade)
at FoxCentral.Web.Filters.DbMigrationFilter.Configure(Action`1 next) in D:a1sFoxCentral.WebFiltersDBMigrationFilter.cs:line 34
at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
at FoxCentral.ServiceHost.RpaWindowsService.OnStart(String[] args) in D:a1sFoxCentral.ServiceHostRpaWindowsService.cs:line 93
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.ServiceProcess.ServiceBase.Run(ServiceBase[] services)
at System.ServiceProcess.ServiceBase.Run(ServiceBase service)
at FoxCentral.ServiceHost.Extensions.HostExtensions.RunAsRpaService(Func`1 host, LoggerConfiguration logConfiguration, String startupMessage) in D:a1sFoxCentral.ServiceHostExtensionsHostExtensions.cs:line 28
at RpaCentral.ServiceHost.Program.Main(String[] args) in D:a1sFoxCentral.ServiceHostProgram.cs:line 95
Error Number:1801,State:3,Class:16

That is interesting. I wonder how it got in this state. Did you manually move the DB files around as part of the install?

Anyways, here are a couple things to try:

  • Restart the machine

  • If that does not work, try:

    1. Move the DB files out of C:WindowsSystem32configsystemprofile.

    2. Start RPAC service. RPAC will try to create the new DBs which will be empty.

    3. Stop the service.

    4. Move the original DB files back to C:WindowsSystem32configsystemprofile and restart the service.

Could you please let us know how that goes?


Thank you!


  1. Make sure Nintex RPA Central was installed as a Windows Administrator. Also, if this is a new install, make sure the first time accessing Nintex RPA Central is also with this same user.

  2. Make sure the machine is connected to a Domain at the time of install. (VPN may be required)

  3. Start Nintex RPA Central service, hoping it starts Running.

  4. Check the Event Viewer for more information.

Please let us know if these solve your problem, or if you have questions about any of these steps.

It looks like you may have already received assistance. If you need anything help let us know. Thanks!