The SmartConnect Setup Wizard ended
Tom asked 3 years ago
Greetings –
I am reinstalling smart connect on a server where I am having some issues. I have deleted the old SC database and user and now I am just trying to recreate the database on the server.
It is erroring out with the “SC Setup Wizard ended”. Is there a log file I can check to see why? If not, does anyone know why this is happening? I have cleaned up SQL Server as far as I can tell (the database and user are gone).
I am reinstalling smart connect on a server where I am having some issues. I have deleted the old SC database and user and now I am just trying to recreate the database on the server.
It is erroring out with the “SC Setup Wizard ended”. Is there a log file I can check to see why? If not, does anyone know why this is happening? I have cleaned up SQL Server as far as I can tell (the database and user are gone).
Answers
Ethan Sorenson Staff answered 3 years ago
Tom,
This article goes over the common causes for this error message.
Another setting to check is if the credentials used to connect to SQL are SQL credentials, and NOT an Active Directory user.
This article goes over the common causes for this error message.
Another setting to check is if the credentials used to connect to SQL are SQL credentials, and NOT an Active Directory user.
Tom replied 3 years ago Thanks Ethan – I already checked those items. Neither the SQL user nor the database exist.
Tom answered 3 years ago
Ethan,
If you read the original post I said that I had checked that. There is no SmartConnect Database or user.
Would orphan services cause this issue?
If you read the original post I said that I had checked that. There is no SmartConnect Database or user.
Would orphan services cause this issue?
Ethan Sorenson Staff replied 3 years ago Tom,
Does the install work if you manually create a blank a blank SmartConnect database and SmartConnect user. Then use these credentials when installing SmartConnect. In some environments we cannot create the database due to security limitations. We usually see this issue if SQL is in Azure.