Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PSConfig upgrade failure with special characters db credentials #63

Open
jokersplusone opened this issue Jun 24, 2020 · 2 comments
Open

Comments

@jokersplusone
Copy link

We're running into the following while trying to run autospinstaller on a SP 2019 box.
The box was previously setup and is working correctly, however the search feature was not installed. I'm trying to
get it installed by enabling search in the .xml and running autosp a second time.

We think the issue is with the password used to access the database, it has special characeters ie:
'a=XXXX,XXXXXX]XXXX.XXX{;', i think the '=' is the culprit. However all the self test worked and the systeem was setup using this password.

We're using database authentication instead of integrated Windows, because this is running on Azure and using a SQL Managed Instance.
The password pass the self test that autosp runs at start.
I've tried running the sp installer with diffeernt db credentials in the .xml file however it's the same problem.

I've tested this on a dev system and it works which is even more confusing
Stack Trace attached
sp_upgrade_log.txt

@jokersplusone jokersplusone changed the title PSConfig upgrade failure with invalid db credentials PSConfig upgrade failure with special characters db credentials Jun 24, 2020
@brianlala
Copy link
Owner

Simply put, you're running too much of the script if all you're looking to do is provision Search. Try following the steps here for only running the specific function to set up Search: https://spinsiders.com/brianlala/2014/04/30/autospinstaller-for-specific-config-changes/

See if that helps get past the error.

@jokersplusone
Copy link
Author

thanks will try, need to schedule it since i can only reproduce issue on a "production" system

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants