eGroup » Central Administration http://www.egroup-us.com Technology Solutions for Serious Competitors Thu, 16 May 2013 18:43:44 +0000 en-US hourly 1 http://wordpress.org/?v=3.5.1 SHAREPOINT .NET ERROR WHEN LOADING CENTRAL ADMINISTRATION. Could not write to output file ‘The directory name is invalid.’ http://www.egroup-us.com/2009/03/sharepoint-net-error-when-loading-sharepoint-central-administration-could-not-write-to-output-file-the-directory-name-is-invalid/ http://www.egroup-us.com/2009/03/sharepoint-net-error-when-loading-sharepoint-central-administration-could-not-write-to-output-file-the-directory-name-is-invalid/#comments Wed, 18 Mar 2009 13:59:31 +0000 Jason Webster http://blogs.eGroup-us.com/?p=488 I recently came across the issue where after a fresh and successful install of SharePoint Server 2007 (MOSS2007) that the Central Administration Site would give an application error upon loading for the first time.  After changing <customErrors mode=”Off” /> in all the web.config files we are able to see the “Could not write to output [...]

The post SHAREPOINT .NET ERROR WHEN LOADING CENTRAL ADMINISTRATION. Could not write to output file ‘The directory name is invalid.’ appeared first on eGroup.

]]> I recently came across the issue where after a fresh and successful install of SharePoint Server 2007 (MOSS2007) that the Central Administration Site would give an application error upon loading for the first time.  After changing <customErrors mode=”Off” /> in all the web.config files we are able to see the “Could not write to output file ‘The directory name is invalid.’” error pointing to a folder below the WindowsMicrosoft.Net directory.  This error indicates that something is amiss with the ASPNET user account and it doesn’t have permissions to write to the folders below the Microsoft.Net folder.  To solve this follow these simple steps.

  1. Open up Computer Management and verify that the user ASPNET exists.
  2. Navigate to the Microsoft.Net directory (typically C:WindowsMicrosoft.Net) and open up it’s security properties.
  3. Add the ASPNET user under the sercurity tab and give it read/write/modify rights.
  4. Click on advanced and check the box to replace permissions on child folders.

Restart IIS and then navigate back to the Central Administration Site and it should be come right up (after a little compile time).

The post SHAREPOINT .NET ERROR WHEN LOADING CENTRAL ADMINISTRATION. Could not write to output file ‘The directory name is invalid.’ appeared first on eGroup.

]]> http://www.egroup-us.com/2009/03/sharepoint-net-error-when-loading-sharepoint-central-administration-could-not-write-to-output-file-the-directory-name-is-invalid/feed/ 0 SharePoint and SSRS Integration error: “An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode.” http://www.egroup-us.com/2009/03/sharepoint-and-ssrs-integration-error-an-unexpected-error-occurred-while-connecting-to-the-report-server-verify-that-the-report-server-is-available-and-configured-for-sharepoint-integrated-mode/ http://www.egroup-us.com/2009/03/sharepoint-and-ssrs-integration-error-an-unexpected-error-occurred-while-connecting-to-the-report-server-verify-that-the-report-server-is-available-and-configured-for-sharepoint-integrated-mode/#comments Thu, 12 Mar 2009 14:15:27 +0000 Jason Webster http://blogs.eGroup-us.com/?p=457 When attempting to Integrate MOSS 2007 with SQL Server 2005 Reporting Server in SharePoint integrated mode there seems to be a few reasons that the above error can occur.  Most of the solutions out there are permissions related by making sure your SSRS application pools are running as a domain user with adequate rights, If you [...]

The post SharePoint and SSRS Integration error: “An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode.” appeared first on eGroup.

]]> When attempting to Integrate MOSS 2007 with SQL Server 2005 Reporting Server in SharePoint integrated mode there seems to be a few reasons that the above error can occur.  Most of the solutions out there are permissions related by making sure your SSRS application pools are running as a domain user with adequate rights, If you are using the Kerberos option you mat have to set up the SPN with the SETSPN commands,  Make sure “Trusted Site” is selected in step 1 of the configuration in SharePoint, etc…

Those have been covered alot and more than likely you have already tried some of them.  One option that I found that wasn’t reported on as often but has fixed my problems in a few installations is force IIS to use NTLM as your authentication method.  If you are attempting to use NTLM as your authentication method and you are getting a 401.1 Authentication error or the above error message from SharePoint.  Follow these steps and see if your issue isn’t resolved.  By this time you have beaten your head against the wall for about a day as I have and anything is worth a shot.  This was the magic bullet for me.

  1. Open up the command line.
  2. Navigate to C:inetpubAdminScripts
  3. exceute the following command (and restart IIS afterwards for good measure)

     cscript adsutil.vbs set w3svc/NTAuthenticationProviders “NTLM”

Navigate back to the MOSS Central Administration Site and see if you are still receiving the error.

Good Luck!

The post SharePoint and SSRS Integration error: “An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode.” appeared first on eGroup.

]]> http://www.egroup-us.com/2009/03/sharepoint-and-ssrs-integration-error-an-unexpected-error-occurred-while-connecting-to-the-report-server-verify-that-the-report-server-is-available-and-configured-for-sharepoint-integrated-mode/feed/ 0