RE: Fails to create portal

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I hope someone has responded to Jonathan before now, but in case anyone else
runs into this issue, I found it was the result of MSDE not being configured
to use TCP/IP.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;832808 - the
error message in the kb article is not the "PortalXMLTemplate" error that I
got, but the fix it suggested finally got the portal creation to get past 50%
and succeed!

To configure SQL Server to use TCP/IP, I used the Client Network for SQL
Server utility on the MSDE server.

Mary F.

"Jonathan Gearinger" wrote:

> Hello,
> Got a situation and heard someone here might be able to help. I have a
> 2003 Server which servers web, exchange and AD. When I tried adding Portal
> Server 2003 it installed AOK and I manually setup the MSDE server.
> Everything attaches and the admin pages work fine except when I try creating
> my initial portal. I have tried it on multiple sites which I had every
> permission selected. The SQL server has all the permissions open.
>
....

> 21:30:58 Exit InitCategories()
....

> 21:31:00 Portal creation job exception. (status=PortalAdminJobStatusFailed)
> System.NullReferenceException: Object reference not set to an instance of an
> object. at Microsoft.SharePoint.Portal.Install.i.a(PortalContext A_0, SPSite
> A_1, PortalXmlTemplate A_2, String A_3, Boolean A_4) at
> Microsoft.SharePoint.Portal.Install.i.a(PortalContext A_0, SPSite A_1,
> String A_2, String A_3, Boolean A_4) at
> Microsoft.SharePoint.Portal.Install.i.a(IDictionary A_0) at
> System.Configuration.Install.Installer.Install(IDictionary stateSaver) at
> System.Configuration.Install.TransactedInstaller.Install(IDictionary
> savedState)
> 21:31:00 Failed to create portal successfully tester
> 21:31:00 Portal creation complete. (Status: PortalAdminJobStatusFailed)
>
>
.

Quantcast