locked
Database already exists error RRS feed

  • Question

  • This may be because I'm misunderstanding the deployment model but I have 3 servers, A, B and C. A and B are load balanced web servers and C is an application server.

    I installed the Platform role of CRM 4.0 on server C and all went well. I then started installing the Application role on server A and it failed at the system requirements stage with an error that the configuration database already exists on the sql server, which is correct. Maybe my mindset is stuck on how SharePoint deployment works but I thought it would detect the database and update it with itself and the role it's performing, but I can't go any further.

    How do I deploy the Applcation role to servers A and B and the platform role to C? Am I even deploying this properly?
    Thursday, June 11, 2009 8:18 AM

Answers

  • Hi.

    I gave up with the multiple server install and settled for installing all the roles on one server for now. Not what I wanted but it's not going to be hammered so I'll leave it at that for now. Thanks.
    Thursday, June 18, 2009 1:35 PM

All replies

  • Have you tried to connect to the existing installation during the setup on server A or have you tried a full install of the app-role?

    You can try following config snippet for installation
    <CRMSetup>
     <Server>
      <SqlServer>SQLServer</SqlServer>
      <database create=”false” />
      <InstallDir>c:\Program Files\Microsoft CRM</InstallDir>
      <Roles>
    	<Role name=”AppServer”/>
    	<Role name=”SDKServer” />
      </Roles>
     </Server>
    </CRMSetup>
    Thursday, June 18, 2009 10:56 AM
  • Hi.

    I gave up with the multiple server install and settled for installing all the roles on one server for now. Not what I wanted but it's not going to be hammered so I'll leave it at that for now. Thanks.
    Thursday, June 18, 2009 1:35 PM