This has certainly been a week. So I was given a new SharePoint 2010 farm by a client (due to a previous adventure, which I will post), but they
did not set up a new database instance. My coworkers did not notice this until late into the evening when they realized the databases would have the same names. I advised them to ask the client for a new instance, so we can start with a stronger foundation
for the new farm, rather than piles of risk.
The client did set up a new instance, but I am not sure how they hooked the app and web servers to the new farm, and what they did to remove them from the old farm (I honestly would have preferred all fresh VMs). My coworker called me tonight to ask for some help on creating the service applications, and all the ones we needed created correctly, except for the managed metadata service.
For whatever reason, no matter what we name the service database, and no matter what managed account we use, the creation of that service results in an error that says, "sharepoint database named whateverDB already exists."
The only information I can find online so far is related to content db's, and issues involving upgrading from 2010 to 2013. I feel like this farm was not as freshly built as it should have been, but I'm not really sure what could have been done to the farm to make it behave this way. Has anyone encountered this error before?
The client did set up a new instance, but I am not sure how they hooked the app and web servers to the new farm, and what they did to remove them from the old farm (I honestly would have preferred all fresh VMs). My coworker called me tonight to ask for some help on creating the service applications, and all the ones we needed created correctly, except for the managed metadata service.
For whatever reason, no matter what we name the service database, and no matter what managed account we use, the creation of that service results in an error that says, "sharepoint database named whateverDB already exists."
The only information I can find online so far is related to content db's, and issues involving upgrading from 2010 to 2013. I feel like this farm was not as freshly built as it should have been, but I'm not really sure what could have been done to the farm to make it behave this way. Has anyone encountered this error before?










