?
Solved

Sharepoint Install failed with SBS r2

Posted on 2006-10-27
6
Medium Priority
?
2,025 Views
Last Modified: 2008-02-03
Using new R2 media DVD from M$ action pack.

I'd done the migration successfully, and was about to migrate my data and got the new R2 media with my maps.

Installed SBS again, redid the swing.

However, on completing the SBS install, the installation of sharepoint doesn't work.

I get a warning in the app event log which says:

Event Type:      Warning
Event Source:      MsiInstaller
Event Category:      None
Event ID:      1015
Date:            28/10/2006
Time:            3:08:18 PM
User:            GOLDRUSH\username
Computer:      ISAIAH
Description:
Failed to connect to server. Error: 0x800401F0

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


In the errorlog.txt  the last entry is:

[10/28/06,15:04:32] Intranet: [2] _SBSDnsCreateCNAMERecord failed in CClientX::DoInstall  hr=  [800725ed]

I used the M$ KB article 897877 to completing remove sharepoint and reinstall it and get the same error.

The sharepoint msde instance installs and is running.

Sharepoint Central Administration Website is created

Companyweb website is not created in IIS.
Companyweb folder is created in inetpub, but is empty.

When I open http://companyweb I get the intro page, but when I click on the "go to my company intranet site" link, nothing happens.

stsadminapppool is created in IIS.

The server is running under vmware, but this shouldn't have any impact on the install. The previous install (not R2) worked fine.

I've googled the error messages and found nothing. The only thing unique about this install is the swing migration (which went smooth as).

Any ideas?

JJ
0
Comment
Question by:micahsdad1402
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
6 Comments
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 17824756
Well, http://companyweb should NOT open "the intro page".  It's supposed to open the Companyweb SharePoint page.

The error seems quite clear to me though, that the CName Record was not created in your DNS.  I'm not sure why that happened, but try just entering it manually and see if that fixes your problem.

Open your DNS Admin > SERVER > Forward Lookup Zones > Domain.local.  

There needs to be an Alias (CNAME) record listed here for companyweb that looks like this:

companyweb                          Alias (CNAME)                 server.domain.local.


So, if there isn't, right click in that pane, and select New Alias.  Put companyweb in the top box and  server.domain.local. (using your real info) in the lower box -- including the trailing period.

That should fix the problem for you.  But perhaps this Alias wasn't able to be added because permissions are wrong on the DNS server?  To check this, in DNS Admin, right click on the Server and select Properties > Security.  Make sure that SYSTEM and Domain Admins have full control.  If SYSTEM or Domain Admins are not listed, click the Advanced Button and then click the DEFAULT button to restore Default Permissions settings.

Jeff
TechSoEasy

0
 
LVL 2

Author Comment

by:micahsdad1402
ID: 17824791
Jeff,

companyweb is in the dns.
Problem is the website doesn't get setup. No companyweb website in IIS and no files in the c:\inetpub\companyweb folder.

Permissions are all OK with DNS. These were all imported from my old servers AD which worked fine. I suspect it is an issue with the R2 install CD.

JJ

FYI company web gets the default page in IIS (because the companyweb website is not setup, so it opens the default page.

  My Company's Internal Web Site
 Collaborate and share documents on your company's internal Web site.
   
  Network Configuration Wizard
 Join a client computer to the Windows Small Business Server network.
   
  Remote Web Workplace
 Connect to the Windows Small Business Server network over the Internet.
   
  Information and Answers
 Learn more about Windows Small Business Server.
 
0
 
LVL 2

Author Comment

by:micahsdad1402
ID: 17861591
I called M$ support.

Turned out the install was failing because I had an A record pointing companyweb to the sbs server, and the install failed on the creation of the cname record and just stopped.

M$ didn't charge me for the call and will update KB Article 829114 (I got the number wrong in my first post.)
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 17868754
Hey there... sorry I missed your Oct 28 post because I would have realized that was the problem if http://companyweb took you anywhere if it wasn't set up.  You would normally get a server not found error.

Glad it's fixed though... and I think you shouldn't use a $ in Microsoft if you are getting free support.  :-)

Jeff
TechSoEasy
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 18189595
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A lot of problems and solutions are available on the net for the error message "Source server does not meet minimum requirements for migration" while performing a migration from Small Business Server 2003 to SBS 2008. This error pops up just before …
You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question