1066 error is thrown when trying to start BWC via Windows services or IC Server manager. No error logs are created. How do I debug this?
Article ID: KB0090353
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks Collaborator | - |
| Not Applicable | - |
Description
Resolution:
1066 error is thrown when trying to start BWC via Windows services or IC Server manager. No error logs are created.
In the Windows services MS SQL Server was using a different user account in "Log On" tab and not local account.
Changing BWC Service to use the same user account as MS SQL Server did help in this case.
Service 1066 error sometimes happens due to authentication and/or login issues. Check if the SQL Server is using Windows or SQL Server Authentication. It should be Windows Authentication. If so, check Services to see if MSSQLSERVER is using Local or 'This Account' login properties.
1066 error is thrown when trying to start BWC via Windows services or IC Server manager. No error logs are created.
In the Windows services MS SQL Server was using a different user account in "Log On" tab and not local account.
Changing BWC Service to use the same user account as MS SQL Server did help in this case.
Service 1066 error sometimes happens due to authentication and/or login issues. Check if the SQL Server is using Windows or SQL Server Authentication. It should be Windows Authentication. If so, check Services to see if MSSQLSERVER is using Local or 'This Account' login properties.
Issue/Introduction
1066 error is thrown when trying to start BWC via Windows services or IC Server manager. No error logs are created. How do I debug this?
Feedback
Yes
No
Powered by
