|
Home > Archive > Microsoft Content Management Server > July 2007 > New Microsoft Office SharePoint Server 2007 Installation Problems
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
New Microsoft Office SharePoint Server 2007 Installation Problems
|
|
| dahazeman 2007-07-03, 7:18 pm |
| I've had some real bad luck installing MOSS and SQL Server 2005. I
tried sandboxing MOSS with SQL 2005 EE, but unfortunately, our MCMS
database is over 6 gigs, and EE has a limit of 4 Gigs per database. So
I started with a fresh operating system again, and went at it. I tried
the Sql 2005 trial version, and developer version, but constantly had
my installations fail.
Regardless, I got past that by installing the developer edition on a
development PC and using that as my database server for MOSS on the
test server. So far so good..everything installed ok, SharePoint
databases included. But when it first fired up Central Administration,
I got an exception:
Runtime Error
Description: An application error occurred on the server. The current
custom error settings for this application prevent the details of the
application error from being viewed.
Details: To enable the details of this specific error message to be
viewable on the local server machine, please create a <customErrors>
tag within a "web.config" configuration file located in the root
directory of the current web application. This <customErrors> tag
should then have its "mode" attribute set to "RemoteOnly". To enable
the details to be viewable on remote machines, please set "mode" to
"Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a
custom error page by modifying the "defaultRedirect" attribute of the
application's <customErrors> configuration tag to point to a custom
error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
I edited the web.config file: <customErrors mode="Off" />
Semi-successful...but then I got this exception:
Compilation Error
Description: An error occurred during the compilation of a resource
required to service this request. Please review the following specific
error details and modify your source code appropriately.
Compiler Error Message: CS0006: Metadata file 'C:\WINDOWS\assembly
\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a
\System.EnterpriseServices.dll' could not be found
Source Error:
[No relevant source lines]
I looked, but the System.EnterpriseServices folder does not exist
inside the GAC_32 folder. Everything is brand spankin' new...why
didn't MOSS install that folder?
What can I do? I can't find any relevant information on this problem.
Thanks,
Jason
| |
| dahazeman 2007-07-04, 1:17 pm |
| I got it! All I had to do was run the .NET Framework 2.0 installation
program and select the Repair option. After a reboot, this exception
went away. I guess the uninstallation of MOSS earlier on had corrupted
the .NET Framework installation.
On Jul 3, 4:30 pm, dahazeman <hazyshadeofg...@hotmail.com> wrote:
> I've had some real bad luck installing MOSS and SQL Server 2005. I
> tried sandboxing MOSS with SQL 2005 EE, but unfortunately, our MCMS
> database is over 6 gigs, and EE has a limit of 4 Gigs per database. So
> I started with a fresh operating system again, and went at it. I tried
> the Sql 2005 trial version, and developer version, but constantly had
> my installations fail.
>
> Regardless, I got past that by installing the developer edition on a
> development PC and using that as my database server for MOSS on the
> test server. So far so good..everything installed ok, SharePoint
> databases included. But when it first fired up Central Administration,
> I got an exception:
>
> Runtime Error
> Description: An application error occurred on the server. The current
> custom error settings for this application prevent the details of the
> application error from being viewed.
>
> Details: To enable the details of this specific error message to be
> viewable on the local server machine, please create a <customErrors>
> tag within a "web.config" configuration file located in the root
> directory of the current web application. This <customErrors> tag
> should then have its "mode" attribute set to "RemoteOnly". To enable
> the details to be viewable on remote machines, please set "mode" to
> "Off".
>
> <!-- Web.Config Configuration File -->
>
> <configuration>
> <system.web>
> <customErrors mode="RemoteOnly"/>
> </system.web>
> </configuration>
>
> Notes: The current error page you are seeing can be replaced by a
> custom error page by modifying the "defaultRedirect" attribute of the
> application's <customErrors> configuration tag to point to a custom
> error page URL.
>
> <!-- Web.Config Configuration File -->
>
> <configuration>
> <system.web>
> <customErrors mode="On" defaultRedirect="mycustompage.htm"/>
> </system.web>
> </configuration>
>
> I edited the web.config file: <customErrors mode="Off" />
> Semi-successful...but then I got this exception:
>
> Compilation Error
> Description: An error occurred during the compilation of a resource
> required to service this request. Please review the following specific
> error details and modify your source code appropriately.
>
> Compiler Error Message: CS0006: Metadata file 'C:\WINDOWS\assembly
> \GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a
> \System.EnterpriseServices.dll' could not be found
>
> Source Error:
>
> [No relevant source lines]
>
> I looked, but the System.EnterpriseServices folder does not exist
> inside the GAC_32 folder. Everything is brand spankin' new...why
> didn't MOSS install that folder?
>
> What can I do? I can't find any relevant information on this problem.
>
> Thanks,
> Jason
|
|
|
|
|