MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Anyone install MOSS 2007 Beta2?

  Asked By: Stacey    Date: Sep 05    Category: MOSS    Views: 671

I've been trying to install MOSS 2007 Beta2 in a dev environment, and
it's dying in the Configuration Wizard (after install).

The log file shows several of the following:
05/25/2006 15:16:30 8 ERR An exception
occurred while provisioning Shared Service Provider 'SharedServices1'.
System.Data.SqlClient.SqlException: Cannot open database
"SharedServices1_DB_1587710c-1193-44a5-9830-2a76be0d9bb2" requested by
the login. The login failed.
Login failed for user 'MOSS\Administrator'.

I had done this:
Created a VMware machine 512MB RAM, 15GB HD,
Installed Windows Server 2003 Standard,
Performed all MS online updates,
Repaired .NET 2.0 (to register .NET 2.0 in IIS),
Installed winfxsetup.exe,
Installed WindowsServer2003-KB912818-v3-x86-ENU.exe (as suggested by
Installed MOSS 2007 as basic single server (SPS32-EN MOSS 2007
Launched into Configuration Wizard,
After lots of time and at the very end of the Wizard's progress bar I
get that error.



9 Answers Found

Answer #1    Answered By: Karla Morrison     Answered On: Sep 05

Do you have database creator rights on the SQL server? Did you enter the
correct user name and password for the SQL account?

Answer #2    Answered By: Patricia Richardson     Answered On: Sep 05

I installed the "Basic" version, so there weren't really any choices.

I tried yet again after I rebooted (before starting the Configuration
Wizard), and I upped the memory in the VM to 1GB. I was running at
512MB which I suspect was the real problem. After I viewed the web
site for the first time, I noticed that it was sitting at 1.3GB
utilization (yikes).

Hopefully I can turn off some services and make room for VS 2005 and
Office Pro Plus v12.

Answer #3    Answered By: Damon Garner     Answered On: Sep 05

From what I’ve seen, B2 is still a hog with memory. Saw an instance where a 4GB machine was steadily using 3GB of the allotted 4GB.

There’s no way MOSS will run at 512, you’re VPC will need at least 1GB, ideally more.

Answer #4    Answered By: Christop Mcfadden     Answered On: Sep 05

Does that VPC have sql server on it. I’m wondering which is the real hog. SQL server or SharePoint. I know that SQL likes to sprawl out into all the memory it can get.

I’m trying to get my VMWare up and running today. I’m about to give up on longhorn and just use 2003.

Answer #5    Answered By: Stefanie Ruiz     Answered On: Sep 05

SQL does seem to be the main culprit here. I have a few VPC's set up to run this and although I havnt had a chance to do any real performance testing ( this is a vpc for gods sakes ) It does appear that the SQL runs fairly hot. Typical. I am currently attempting to break up the systems and run on seperate instances of VPC but you can only stretch 1 Gig of Memory so far ;)

One system ran everything... AD... SQL... MOSS... On a version 2.0 implementation this did not seem to be an issue..... Let the testing begin

Answer #6    Answered By: Damon Garner     Answered On: Sep 05

I have Longhorn installed on a VM right now. It look most of a day to do so, but once it was installed it moves much faster.

Answer #7    Answered By: Royce Orr     Answered On: Sep 05

I have a 2-VPC setup… 1 running AD & SQL 2005 SP1 with 400MB allocated and another B2 box running just MOSS B2 w/ 1024MB RAM.

However, with that being said, I also have a MOSS B2 VPC running as well with SQL on the same VPC, but no AD.

Answer #8    Answered By: Laura Walker     Answered On: Sep 05

From what I’ve heard, stay away from installing B2 on Vista until after B2TR… you’ll run into problems down the road. Stay with Win2003 R2.

Answer #9    Answered By: Peter Peterson     Answered On: Sep 05

SQL server is very good about getting out of the way when necessary.

Didn't find what you were looking for? Find more on Anyone install MOSS 2007 Beta2? Or get search suggestion and latest updates.