Unable to sign into App Store [Solved]
Posted: Fri Mar 03, 2023 8:15 pm
Long story short, the server we had Switch installed on crapped out on us - specifically the OS drive died. We had the Application Root on a different drive, thankfully.
I installed Switch on the new server and opened it up for the first time and signed into the App Store and it signed in successfully. I then shut down the Switch server applications and ran the Application Data Root tool to set a new data root, which is on the separate drive.
Originally, with the settings I had in there, SSL was turned on. When I opened the Switch application, it told me there was a hardware change and I needed to sign in again. When I signed in, it was giving me a "Connection Refused" error with code 10061. I then turned off SSL and now, when I sign in, I'm getting a 500 error instead.
I am working with Enfocus Support but I was hoping that someone else has had this problem and could get back to me with a solution quicker than support. Based on a log file, support told me to rename my "UserDatabase.db3" and let it generate a new one, which it did, but that didn't fix it.
Any thoughts from anyone that has had this problem and can tell me how they fixed it?
I installed Switch on the new server and opened it up for the first time and signed into the App Store and it signed in successfully. I then shut down the Switch server applications and ran the Application Data Root tool to set a new data root, which is on the separate drive.
Originally, with the settings I had in there, SSL was turned on. When I opened the Switch application, it told me there was a hardware change and I needed to sign in again. When I signed in, it was giving me a "Connection Refused" error with code 10061. I then turned off SSL and now, when I sign in, I'm getting a 500 error instead.
I am working with Enfocus Support but I was hoping that someone else has had this problem and could get back to me with a solution quicker than support. Based on a log file, support told me to rename my "UserDatabase.db3" and let it generate a new one, which it did, but that didn't fix it.
Any thoughts from anyone that has had this problem and can tell me how they fixed it?