Ronel_Data Posted December 7 Posted December 7 We have FM Pro 19.6.3.302, FM Server 19.5.2 running on a Windows Server 2016 Std VM. The configuration goes through perfectly for the database we are trying to get to deploy. We currently have the "Test" database in a local folder on the Desktop. The "Production" server is the FM Server on the same VM. (Set up this way for testing.) Both databases have the exact same and the exact same login accounts. The login account being used for deployment does have Full Access privileges in other databases. When clicking the deploy button in the 360Deploy datable, an error is displayed rather consistently. I did notice that there is a different database that the login account does not get access to. This other database is irrelevant to the deployment. I mention it just in case it is part of the problem. Thing is, when I create a new database, the deployment works very well. Also, the 360Deploy demo solution database does deploy successfully, too. Any insights? The final set up would be to deploy from an actual Test FM Server (which is what I am currently using as the "Production" server for testing) to an actual separate Production FM Server. I would like to make sure things are working before testing from the actual Test FM Server to the actual Production FM Server. Thanks for your help! --Raf Batista
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now