>> Do you think any of that is going to have an affect on a configuration error?
Probably not Matt, but "then ask for a backup from the original configuration and restore that into your VM." really is great advice from Jeff and what I would probably do if I completely gave up and couldn't get this working. Setup my own clean farm that I know is working and then restore a site collection backup, or db backup to it. Although, the problem sounds to me like its database connection errors, but it could be a number of reasons really. I hate when SharePoint completely dies like this, but it's so common. This may be your best resource - Plan for administrative and service accounts (Windows SharePoint Services) Updated: June 14, 2007 http://technet2.microsoft.com/Office/f/?en-us/library/89e4c579-5720-45e0-917e-abeb95266c3e1033.mspx The account you are using during setup, and other accounts you enter during the configuration wizard require special privileges on your DB server and Databases, so do App Pool accounts : Account Server farm standard requirement Least-privilege when connecting to pre-created databases requirements Setup user account * Domain user account. * Member of the Administrators group on each server on which Setup is run. * SQL Server login on the computer running SQL Server. * Member of the following SQL Server security roles: * securityadmin fixed server role * dbcreator fixed server role If you run Stsadm commands that affect a database, this account must be a member of the db_owner fixed database role for the database. Server farm standard requirements with the following additions or exceptions: * Use a separate domain user account. * NOT a member of the Administrators group on the computer running SQL Server. This account is used to configure databases. After each database has been created, change the database owner (dbo or db_owner) to the Setup User account. Server farm account * Domain user account. * If the server farm is a child farm with Web applications that consume shared services from a parent farm, this account must be a member of the db_owner fixed database role on the configuration database of the parent farm. Additional permissions are automatically granted for this account on Web servers and application servers that are joined to a server farm. This account is automatically added as a SQL Server login on the computer running SQL Server and added to the following SQL Server security roles: * dbcreator fixed server role * securityadmin fixed server role * db_owner fixed database role for all databases in the server farm Server farm standard requirements with the following additions or exceptions: * Use a separate domain user account. * NOT a member of the Administrators group on any server in the server farm, including the computer running SQL Server. * This account does not require permissions to SQL Server before creating the configuration database. After the Shared Services Provider (SSP) database and the SSP search database are created, add this account to the following for each of these databases: * Users group * db_owner fixed database role Additional application pool identity accounts Account Server farm standard requirement Least-privilege when connecting to pre-created databases requirements Application pool identity No manual configuration is necessary. The following are automatically configured: * Membership in the db_owner role for content databases and search databases associated with the Web application. * Access to read from the configuration and the SharePoint_AdminContent databases. * Additional permissions for this account to front-end Web servers and application servers are automatically granted. Server farm standard requirements with the following additions or exceptions: * Use a separate domain user account for each application pool. * This account should not be a member of the Administrators group on any computer in the server farm. After the SSP database and the SSP search database are created, add this account to the following for each of these databases: * Users group * db_owner role Sezai Kömür Senior Developer - BEng, BSc - Microsoft Certified Technology Specialist - http://www.moss2007.com.au/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Lynch Sent: Tuesday, 11 December 2007 7:12 PM To: [email protected] Subject: RE: [OzMOSS] Virtual Server Image Out of curiosity, Do you think any of that is going to have an affect on a configuration error? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Headley Sent: Tuesday, 11 December 2007 9:04 PM To: [email protected] Subject: RE: [OzMOSS] Virtual Server Image Using a virtual image as a MOSS dev environment is common and offers some advantages. Are you using a Microsoft VM image (vmc/vmd) or VMware? Are all your servers (SQL & MOSS) in the image? If not, you probably won't easily connect to a required server not in the image. If they are, you may want to check what network cards the VM thinks it has, since moving it from one host to another might change these settings if actual (physical) network cards were being used. If that's all fine consider checking your IIS settings for name resolution issues. If the image is incomplete or unusable you might choose to create a new VM that has all the necessary servers, then ask for a backup from the original configuration and restore that into your VM. This works as easily for VMs as it does for actual deployments. As long as your VM has a minimal load (not too many users at once) and enough RAM it can make a great dev platform. In addition you can put it on a server that gets backed up every night (to take away your worries) you can either remote into it or just go in through your browser and use your local copy of SharePoint Designer. Jeff From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of STRINGFELLOW Mike (Con) Sent: Tuesday, 11 December 2007 7:11 PM To: [email protected] Subject: [OzMOSS] Virtual Server Image I've been given a virtual server, an image of another developers MOSS server, as my dev platform. Are there any tricks to get this working? Running Central Admin points to the original boxes hostname and fails, and running the config wizard dies with db connection errors. Accessing the sites also give DB connection errors. It looks as if it is trying to connect to the remote box's DBs (no connection string info in the logs unfortunately), or doesn't have permissions for connections to my Virtual Server's DBs. I haven't found any info on the web, so this doesn't seem this is the normal way of doing things - so I might be re-installing? Any help would be appreciated! ________________________________ Make the switch to the world's best email. Get the new Yahoo!7 Mail now<http://au.rd.yahoo.com/mail/taglines/default_all/mail/spankey/*http:/au.yahoo.com/worldsbestmail/spankey/>. ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
