Quantcast
Channel: Al's Tech Tips
Viewing all 388 articles
Browse latest View live
↧

Error 8193: Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW... Access is denied

December 26, 2013, 11:41 am
$
0
0
Problem

The following error appears in a SharePoint Server 2010 farm server:
Log Name:      Application
Source:        VSS
Date:          [date]
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      [computername]
Description:
Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,...).  hr = 0x80070005, Access is denied.
Operation:
   Initializing Writer
Context:
   Writer Class Id: {0ff1ce14-0201-0000-0000-000000000000}
   Writer Name: OSearch14 VSS Writer
   Writer Instance ID: {ec5611b9-3477-4ae9-8cea-778025228ec5}
.
.
.
Discussion

The error involves a permissions issue, but it isn't immediately obvious what account is being denied access.  The account needs to be determined in order to grant it the appropriate permissions to the service. 

The VSS writer name being OSearch14 VSS Writer indicates that the account is related to the SharePoint Server 2010 (ie, "2010" =  "14") account used to run SharePoint Server 2010 server search.  To correlate this with a specific AD account, review the Services listing to find the service SharePoint Server Search 14, and the logon for this service will be the account in question.  One  can also go to the error Event Properties dialog Details tab in Friendly View mode, and then scrolling down to the In Bytes section: the path to the executable and the account that is running the executable will  be shown to the right.

Solution
  1. Logon to the server as an administrator.
  2. Open Registry Editor on the server.
  3. Navigate to the key HKLM\SYSTEM\CurrentControlSet\Services\VSS\Diag.
  4. Right-click, and then select Permissions.
  5. Add the farm search account.
  6. Set the farm search account to (Allow) Full Control.
  7. Click Apply
  8. Click OK.
References
↧
Search

Error: The feature failed to activate because a list at 'PublishingImages' already exists in this site

December 27, 2013, 4:16 am
$
0
0
Problem

You attempt to activate the Publishing feature for a SharePoint 2010 site,
but experience the following error:
The feature failed to activate because a list at 'PublishingImages' already exists in this site.  Delete or rename the list and try activating the feature again.
You then check All Content for the site and do not find any images library named PublishingImages, but only a standard Images library,
Solution

This experience is by design.  To resolve this problem, follow the guidance suggested in the error message.  Rename the existing Images folder:
Then try activating the site's Publishing feature again.
After the feature has been activated, you will see a new Images library for the site


References
↧
↧

Warning 1015: Failed to connect to server. Error: 0x80070005

December 27, 2013, 6:50 am
$
0
0
Problem

On a daily basis, you see the following warning appear in the SharePoint server 2010 host's Application log:
Log Name:      Application
Source:        MsiInstaller
Date:          [date]
Event ID:      1015
Task Category: None
Level:         Warning
Keywords:      Classic
User:          [SharePoint farm account]
Computer:      [a SharePoint Server 2010 host]
Description:
Failed to connect to server. Error: 0x80070005
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1015</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="..." />
    <EventRecordID>8607</EventRecordID>
    <Channel>Application</Channel>
    <Computer>[a SharePoint Server 2010 host]</Computer>
    <Security UserID="..." />
  </System>
  <EventData>
    <Data>0x80070005</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
  </EventData>
</Event>
You may see a 100 or so similar warnings appear daily, each one accompanied by a corresponding Information event, such as the following:
Log Name:      Application
Source:        MsiInstaller
Date:          [date]
Event ID:      1035
Task Category: None
Level:         Information
Keywords:      Classic
User:          [SharePoint farm account]
Computer:      [a SharePoint Server 2010 host]
Description:
Windows Installer reconfigured the product. Product Name: Microsoft InfoPath Form Services English Language Pack. Product Version: 14.0.7015.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1035</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="..." />
    <EventRecordID>8608</EventRecordID>
    <Channel>Application</Channel>
    <Computer>[a SharePoint Server 2010 host]</Computer>
    <Security UserID="..." />
  </System>
  <EventData>
    <Data>Microsoft InfoPath Form Services English Language Pack</Data>
    <Data>14.0.7015.1000</Data>
    <Data>1033</Data>
    <Data>0</Data>
    <Data>Microsoft Corporation</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
    <Binary>...</Binary>
  </EventData>
</Event>
Each of these pairs corresponds to a different component that can be configured for the farm.

Discussion

These are associated with the farm's Product Version Job, which by default runs daily at 12:45 AM.  Compare the times of these warnings with the time that your farm's Product Version Job runs, and you'll see the association.

Solution
  1. Add the farm account to the host's local administrator group.
  2. Restart the SharePoint 2010 Timer service.
  3. Remove the farm account from the host's local administrator group.
  4. Run the farm's product Version Job.
  5. Check the host's Application Log.
References
Notes
  • Thanks to SP-Jim for finding this solution (scroll down near the bottom).
↧

Error 5161: Site 2 has no root application defined, so the site will be ignored.

December 27, 2013, 7:31 am
$
0
0
Problem

You see the following error appear irregularly in the SharePoint 2010 server Application log:
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          [date/time]
Event ID:      5161
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      [SharePoint 2010 server host machine name]
Description:
Site 2 has no root application defined, so the site will be ignored.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
    <EventID Qualifiers="49152">5161</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="..." />
    <EventRecordID>9077</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>[SharePoint 2010 server host machine name]</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SiteID">2</Data>
    <Binary>0D000780</Binary>
  </EventData>
</Event>
Discussion

The SharePoint Server 2010 installation creates an additional site, SITE_2.  This site can be seen in IIS Manager.  It will create further such sites on removing SharePoint 2010 and subsequently installing it again without removing the SITE_2 website. Thus, you may see a SITE_2, SITE_3, etc.

Solution

These sites can be safely removed using IIS Manager.  Restart IIS after removing these sites.

References
Notes
  • This site seems to be a placeholder for prospective web services deployment.  You can see this by reviewing the ApplicationHosts.Config file at C:\Windows\System32\inetsrv\config.  Scroll down to the <Sites> node to see the Site 2 entry.
↧

InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured

December 30, 2013, 8:24 am
$
0
0
Problem

You find the following entry in the SharePoint 2010 Central Administration Review problems and solutions All Reports listing:

TitleInfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured.
Severity2 - Warning
CategoryConfiguration
ExplanationInfoPath Forms Services is not functional on the following Web applications because there is no service connection configured for the State Service: [servicename]
RemedyIf a State Service application doesn't exist, create one by using the new-SPStateServiceApplication Powershell commandlet. For more information on configuring the State Service, see Help. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142645".
Failing Servers[servername]
Failing ServicesSPTimerService (SPTimerV4)
Rule SettingsView
 
Solution

Create the State Service application and proxy using the following PowerShell script:

$mysa = New-SPStateServiceApplication -Name "State Service"
New-SPStateServiceDatabase -Name "DB_StateService"–ServiceApplication $mysa
New-SPStateServiceApplicationProxy -Name "State Service Proxy" -ServiceApplication $mysa –DefaultProxyGroup


Summary

This posting has presented a PowerShell method for resolving the SharePoint 2010 Health Analyzer warning.  Using the PowerShell method avoids creating a database having a long name that includes a GUID string.  For additional detail on the topics discussed in this posting, see the references below.

References
↧
↧

Health Analyzer: Databases running in compatibility range, upgrade recommended

December 30, 2013, 9:41 am
$
0
0
Problem

You find the following entry in the SharePoint 2010 Central Administration Review problems and solutions All Reports listing:

TitleDatabase has large amounts of unused space.
Severity3 - Information
CategoryAvailability
ExplanationFollowing databases have large amounts of space allocated on the disk but not in use. This may be due to recent deletion of data form the database, or because the database has been pre-grown to a larger size. This database will take up a larger amount of space on the file system unless it is shrunk down to a smaller size. [databasename] on [machinename]
RemedyThe database can be shrunk in size using the DBCC ShrinkDatabase command or the Shrink Database wizard in SQL Server Management Studio. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=167144".
Failing Servers 
Failing ServicesSPTimerService (SPTimerV4)
Rule SettingsView
 
Solution

Depending on the size of the database, run the Shrink Database task in Microsoft SQL Server Management Studio.
  1. Right-click on the database
  2. Go: Tasks > Shrink > Database. 
References
↧

Error 7557: The Secure Store Service application Secure Store Service is not accessible.

December 30, 2013, 11:09 am
$
0
0
Problem

You attempt to generate a new Secure Store key, but when you go to the Manage page for the Secure Store application, you see this error message:
You then check the server's Application event log and see the following error corresponding to each of your attempts to access the Secure Store Application:
Log Name:      Application
Source:        Microsoft-SharePoint Products-Secure Store Service
Date:          [date/time]
Event ID:      7557
Task Category: Secure Store
Level:         Error
Keywords:   
User:          [user]
Computer:      [servername]
Description:
The Secure Store Service application Secure Store Service is not accessible. The full exception text is: There

are no addresses available for this application.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-Secure Store Service" Guid="{...}" />
    <EventID>7557</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="[date/time]" />
    <EventRecordID>11014</EventRecordID>
    <Correlation ActivityID="{...}" />
    <Execution ProcessID="6648" ThreadID="4000" />
    <Channel>Application</Channel>
    <Computer>[servername]</Computer>
    <Security UserID="..." />
  </System>
  <EventData>
    <Data Name="string0">Secure Store Service</Data>
    <Data Name="string1">There are no addresses available for this application.</Data>
  </EventData>
</Event>
Solution
 
This is frequently a permissions issue.  To resolve, perform these checks and procedures:
  1. Check the Secure Store service
    1. Start it if it is stopped
    2. Try accessing the Manage page again.
  2. Check the user account you are currently logged in as:
    1. If it is NOT the farm configuration account, login using the farm configuration account, and then try accessing the Manage page again.  Or,
    2. If it is NOT the farm configuration account, add your administration account to the farm configuration database: Add-SPShellAdmin -UserName [your admin account] -Confirm -WhatIf.  Then try accessing the Manage page again.
    3. If it IS the farm configuration account, stop and restart the Secure Store service, and then try accessing the Manage page again.
Notes
  • Search engine text: Cannot complete this action as the Secure Store Shared Service is not responding. Please contact your administrator.
↧

Error: The trial period for this product has expired.

January 2, 2014, 8:10 am
$
0
0
Problem

Follows are the troubleshooting steps taken in order to resolve the following message that appeared when connecting to a SharePoint 2010 farm site collection using a standard AD user account:
Error: The trial period for this product has expired
The solution to this problem was unexpected and thus documented here.

Farm is SharePoint 2010, version 14.0.7015.1000 (SP2), with topology : SQL1, APP1, WFE1 and WFE2.  New installation.

Troubleshooting Steps
  1. Remoted directly into a farm server, as system administrator, and then connected to Central Administration.  Was able to connect to CA.
  2. Using the same browser, opened tab to connect to site collection.  Successful: site collection home page was displayed.
  3. On workstation, under normal account, opened a new browser and again connected to site collection.  Unsuccessful: same error message displayed.
  4. As systems administrator, remoted into another farm server, opened a browser, and then connected to the site collection.  Unsuccessful: experienced same error.
    Apparently, by first logging into CA and then connecting to the site collection, I was able to bypass the issue causing the problem.  Conclusion:  the root cause of the issue was somehow related to permissions and was not related to a product key that was a trial version and not the fully-licensed enterprise version.
    .
  5. Performed psconfig -cmd secureresources on all farm servers, per reference [1], logged in as the farm administration account. Results were successful on APP1and WFE1, but failed on WFE2 with the following error displayed in the same command prompt used to run the command on WFE2:
    ...
    Successfully secured the SharePoint resources.
    Performing configuration task 4 of 5
    Upgrading SharePoint Products...
    Failed to upgrade SharePoint Products.
    An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20140102-075746-95 was updated by [FarmAdministrationAccount], in the PSCONFIG (736) process, on machine [WFE2]. View the tracing log for more information about the conflict.
     ...
  6. After executing this command, performed IISRESET on all machines.
  7. Attempted to again connect to the farm site collection, but still experienced the error.
  8. Checked machine logs and found the following in the Application log:
    Event ID 100: Configuration of SharePoint Products failed. Configuration must be performed in order for th is product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\PSCDiagnostics_1_2_2014_7_57_34_563_1728581215.log, fix the problem, and run this configuration wizard again.

    Event ID 104: Failed to upgrade SharePoint Products. An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20140102-075746-95 was updated by [FarmAdministrationAccount], in the PSCONFIG (736) process, on machine [WFE2]. View the tracing log for more information about the conflict. Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20140102-075746-95 was updated by [FarmAdministrationAccount], in the PSCONFIG (736) process, on machine [WFE2]. View the tracing log for more information about the conflict. at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.PutObject(SPPersistedObject persistedObject, Boolean ensure) at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Update() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ContinueOnLocalThread(Guid id, Boolean consoleOutput) at Microsoft.SharePoint.Upgrade.SPManager.ContinueSessionOnLocalThread(Guid id, Boolean consoleOutput) at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
    ...
  9. Performed psconfig -cmd upgrade -inplace b2b -wait -force on WFE2, under the farm administration account. This failed with the following error displayed in the command prompt:
    ...
    Performing configuration task 3 of 4
    Upgrading SharePoint Products...
    Failed to upgrade SharePoint Products.
    An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20140102-075746-95 was updated by [FarmAdministrationAccount], in the PSCONFIG (736) process, on machine [WFE2]. View the tracing log for more information about the conflict.
    ....
  10. Reviewed Upgrade Status in Central Administration.  Showed as Failed.
  11. Performed stsadm -o setproperty -pn command-line-upgrade-running -pv No on WFE2, per reference [2], under the sharepoint farm administration account.  This operation completed successfully.
  12. Performed psconfig -cmd secureresources on WFE2 again, followed by IISRESET, under the farm administration account.  Failed with same error as previously.
  13. Reviewed Upgrade Status in Central Administration. Showed as Failed.
  14. Performed psconfig -cmd upgrade -inplace b2b -wait -force on WFE2, under the farm administration account. This failed again, but it failed at a point further along the upgrade process:
    ...
    Performing configuration task 3 of 4
    Upgrading SharePoint Products...
    100.00%
    Failed to upgrade SharePoint Products.
    An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20140102-081022-697.log. The number of errors and warnings is listed at the end of the upgrade log file.
    ...
  15. Reviewed the log file indicated in the error message and found the following:
    ...
    [PSCONFIG] [SPUpgradeSession] [ERROR] [1/2/2014 8:11:06 AM]: CanUpgrade [SecureStoreServiceDatabase Name=SecureStoreDatabaseName] failed.
    [PSCONFIG] [SPUpgradeSession] [ERROR] [1/2/2014 8:11:06 AM]: Exception: Cannot open database "SecureStoreDatabaseName" requested by the login. The login failed.
    Login failed for user 'FarmAdministrationAccount'.
    ...
  16. Reviewed the SecureStore database logins and found that the farm service account was not mapped to this database. Mapped the farm service account as DBO to this database.
    This database had been created using the manual PowerShell method for creating the service application.  Apparently, this method did not grant the farm administration account any permissions to the database.  Checking other service application databases found the same.  Conclusion: the upgrade, while run under the farm administration account, could not be completed because this account did not have permission to update this particular database.
  17. Performed psconfig -cmd upgrade -inplace b2b -wait -force on WFE2, under the farm administration account. This time, successful.
  18. Reviewed Upgrade Status in Central Administration. Showed as Succeeded.
  19. On workstation, opened new browser and connected to farm site collection.  This time no error.
Lessons Learned

May not have performed Psconfig on WFE2 during installation of WFE2.

References
  1. The trial period for this product has expired. Trial Period? WTH?
  2. Configuration wizard failed “An update conflict has occurred, and you must re-try this action.”
  3. Share Point- The trial period for this product has expired
  4. the trial period for this product has expired. sharepoint foundation 2010
  5. Psconfig command-line reference (SharePoint Server 2010)
  6. SharePoint 2010: The trial period for this product has expired
↧
Search

SharePoint 2010: Farm Database Server memory

January 10, 2014, 12:04 pm
$
0
0
Problem

You have installed a new three-tier, SharePoint 2010 farm to virtual machines hosted on Microsoft Hyper-V.  The farm employs SQL Server 2008 R2.  After some time has elapsed, your systems admin informs you that the VM hosting the database server is using 32 GB RAM and this usage continues to climb.  Traffic to the farm is steady and not increasing.

Discussion

SQL Server 2008 R2 can dynamically adjust its buffer pool (cache) size in order to minimize paging.  It will continue to use memory up to that available.  This is normal behavior. 

By default, SQL Server 2008 R2 maximum server memory is set to 2147483647 MB.  If the VM has not been configured for maximum memory, SQL Server will continue to increase its usage of virtual memory to the maximum it can. 

The Maximum Server memory setting configures the buffer pool memory limit.  It does not affect the amount of memory that SQL Server allocates for other processes.

Solution
  1. Launch SQL Server Management Studio.
  2. In Object Explorer, right-click the server name in the tree (top item).
  3. Choose Properties (at bottom of list).  The Server Properties dialog appears.
  4. In the selection pane of the dialog, select Memory.
  5. In the Maximum server memory (in MB) field, enter the maximum memory you want to set.  Set this to less than the actual memory allocated to the VM or physical memory available.  Leave two GB or so for other SQL Server and Windows processes.  See the References for guidance on memory allocation.  You can adjust SQL Server Maximum server memory without restarting the server. 
    After you make this adjustment, server memory usage will drop initially, but then gradually increase again.  This second increase is due to Hyper-V locking the available memory
  6. Click OK.

References
↧
↧

SharePoint Designer 2010: This page cannot be edited in SharePoint Designer

January 13, 2014, 6:19 am
$
0
0
Problem

You connect to a SharePoint 2010 farm site through SharePoint Designer 2010 in order to edit a page at the site.  After successfully connecting to the site and checking out the page, when you then click the Edit link, you experience this prompt:
Solution
  1. On seeing this prompt, click Cancel.
  2. Undo the checkout.
  3. Go to a list view of the pages
  4. Select the page.
  5. On the All Files ribbon, click the Detach from page Layout button.
  6. Proceed to edit as normal.
References
↧

SharePoint 2010: PowerShell scripts for generating farm inventory

January 15, 2014, 12:52 pm
$
0
0
Introduction

In this post, I present PowerShell scripts that I use to generate various listsings, such as sites, lists, permissions, etc.

Inventory Listing of Farm Sites and their Configurations

This script generates a listing of all sites in the farm, across all web applications, that includes such configuration details as: Create Date, Create Author, Template name and ID, RecycleBinEnabled, etc.  There are more fields available than included in this script - to find out all of the available fields, pipe the base script into the Get-Member object.
Add-PSSnapin Microsoft.SharePoint.PowerShell
Get-SPWebApplication http://[your website] | Get-SPSite -Limit All | Get-SPWeb -Limit All | Select Title, Name, Created, URL, ID, ParentWebID, Language, WebTemplate, WebTemplateID, Theme, IsRootWeb, Author, Description, RecycleBinEnabled, SiteAdministrators, SiteGroups | Export-CSV \\[intranet location]\results.csv -NoTypeInformation

Inventory Listing of Farm Lists and their Configurations

This script generates a listing all lists and libraries in the farm.
$SiteLists = foreach ($site in get-spsite) { foreach ($web in $site.AllWebs) { foreach ($list in $web.lists) {$list} } }
$SiteLists | Select parentWebURL, parentWeb, Title, Hidden, Author, Created, itemCount, Description | Export-CSV \\[intranet location]\FileName.csv -NoTypeInformation

References
↧

Health Analyzer: The Visio Graphics Service has a minimum cache age setting that may cause a security issue

January 16, 2014, 5:45 am
$
0
0
Problem

The following issue appears in the SharePoint 2010 Central Administration Review problems andsolutions report:

TitleThe Visio Graphics Service has a minimum cache age setting that may cause a security issue.
Severity1 - Error
CategoryPerformance
ExplanationSetting minimum cache age to 0 minutes may leave the Visio Graphics Service open to a denial of service (DoS) attack. A value of 0 for this setting may lead to large processor and network load of the Visio Graphics Service and SharePoint, decreasing the expected performance of both. However, increasing this value means that users will not see their Web Drawings refreshing as frequently.
The minimum cache age rule for value 0 failed. Visio Services
RemedyThe resolve this issue, the Visio Graphics Service administrator must assign a value greater than 0 minutes to this setting. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142657".
Failing Servers 
Failing ServicesVisioGraphicsService
Rule SettingsView

Solution

You may see this issue appear if, after testing Visio services, you forget to change the cache age settings back to their recommended value ranges.  To solve:
  1. Go to farm Central Administration.
  2. Navigate to: CA > Application Management > Manage Service Applications > Visio Graphics Services Application > Global Settings.
  3. Set Minimum Cache Age to a value > 5 (minutes).
References
↧

Health Analyzer: The Unattended Service Account Application ID is not specified or has an invalid value

January 16, 2014, 9:30 am
$
0
0
Problem

The following issue appears in the SharePoint 2010 Central Administration Review problems andsolutions report:

TitleThe Unattended Service Account Application ID is not specified or has an invalid value.
Severity2 - Warning
CategorySecurity
ExplanationThe Unattended Service Account is a single account that all documents can use to refresh data. It is required when connecting to data sources external to SharePoint, such as SQL. Without a valid Unattended Service Account Application ID, Visio Graphics Services will not be able to refresh Web Drawings that are connected to external data sources.
The rule for the Unattended Service Account Application ID failed. The ID does not exist. Visio Services
RemedyTo resolve this issue, the Visio Graphics Services administrator must provision the Secure Store Service, create a target application, and assign the ID of this target application to this setting. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142617".
Failing Servers 
Failing ServicesVisioGraphicsService
Rule SettingsView

Solution

This issue may occur if the Secure Store Service or Secure Store Target Application have not yet been configured.
  1. In farm Central Administration, navigate to: CA > Application Management > Service Applications > Manage Service Applications > Secure Store Service Application.
  2. Review the available target applications and determine which one to use. 
    If you see the error, "The Secure Store Service application Secure Store Service is not accessible," go to this reference for steps on resolving it.
  3. Note down the Target Application ID associated with the selected target application.  For this posting, VisioGraphicsApp01 is used.
  4. Now navigate to: CA > Application Management > Service Applications > Manage Service Applications > Visio Graphics Service Application > Global Settings.
  5. Enter the Target Application ID above into the Application ID field, and click OK.
  6. Navigate back to: CA > Monitoring > Health Analyzer > Review problems and solutions.
  7. Click on the issue again, then click the Reanalyze Now button, and then click Close.
  8. Wait a few minutes, and then refresh the page.
References
↧
↧

Health Analyzer: Missing server side dependencies

January 16, 2014, 11:09 am
$
0
0
Problem

The following issue appears in the SharePoint 2010 Central Administration Review problems andsolutions report:

TitleMissing server side dependencies.
Severity1 - Error
CategoryConfiguration
Explanation[MissingWebPart] WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663] is referenced [22] times in the database [CA-Content-DB], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CA-Content-DB], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9f56656f-6aa3-0d55-a812-711bf65864ea] is referenced [101] times in the database [CA-Content-DB], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CA-Content-DB], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [874f5460-71f9-fecc-e894-e7e858d9713e] is referenced [63] times in the database [CA-Content-DB], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CA-Content-DB], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
RemedyFor more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142689".
Failing Servers 
Failing ServicesSPTimerService (SPTimerV4)
Rule SettingsView

Solution
  1. In Central Administration, navigate to: CA > Application Management > Manage Service Applications > Search Service Application > Manage.  This takes you to the SearchAdministration page.
  2. Next, navigate to: CA > Application Management > Manage Service Applications > Search Service Application > Manage > Farm Search Administration.  This takes you to the SearchFarmDashboard page.
  3. Then, navigate to: CA > Monitoring > Health Analyzer > Review problems and solutions.
  4. Click the issue link, click Reanalyze Now, and then click Close.
  5. Wait a few minutes, and then refresh the page.
References
↧

SharePoint 2010: Change File Icon

January 18, 2014, 10:47 am
$
0
0
Introduction

This post walks you through the process of changing the icon associated with a file listed in a SharePoint 2010 document library, such as the PDF icon.  Icons for documents listed in a library are typically 16x16 pixels in dimension.  The PDF icon will be changed in this post.

Solution
  1. Download the PDF from the Adobe web site.
  2. In any document library in which PDFs are stored, right click on the PDF icon and choose Properties.
  3. Note the filename for the icon.
  4. For each server in the farm on which SharePoint 2010 is installed:
    1. Navigate to: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES.
    2. Scroll through the images to find the filename identified in step 3 above.
    3. To support rollback if necessary change the name of this file (e.g., filename_OLD.png).
    4. Copy the new icon file to this location.
    5. Rename the file to the same name used by the old file.
    6. Restart IIS.
    7. Verify that the new icon appears as expected.
References
↧
Search

Error 6398: The Execute method of job definition... threw an exception

January 18, 2014, 11:30 am
$
0
0
Problem

This posting details the troubleshooting steps taken to resolve this particular version of error 6398 (below).  

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          date/time
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          [a farm service account]
Computer:      [a farm server]
Description:
The Execute method of job definition 
Microsoft.Office.InfoPath.Server.Administration.FormsMaintenanceJobDefinition 
(ID 47448841-f622-4c46-a01a-17a15800e9b2) threw an exception. More information 
is included below. Access to the path 
'C:\ProgramData\Microsoft\SharePoint\Config\8efbf9e5c7924dcf9f9341a2c482728c'
is denied.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint 
Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
    <EventID>6398</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>

Troubleshooting Steps
  1. Checked each farm server to determine where the issue was occuring.  Found that it only occurred on the farm application server.
  2. Navigated to: C:\ProgramData\Microsoft\SharePoint\Config.
  3. Right-clicked the folder and selected Properties.
  4. Selected the Security tab.  Found two SIDs listed that failed to eventually resolve to any specific user or group name.  Likely corrupted.
  5. Checked the Security tab for the same folders on the other two farm servers and found two groups that appeared in these but not for the application server: WSS_ADMIN_WPG and WSS_WPG.
  6. Added these two groups to the folder and configured their permissions as seen for the other two farm servers.  Left the two unassociated SIDs in place.  Will remove after a week.
References
↧

SharePoint 2010 Health Analyzer: The timer service failed to recycle

January 18, 2014, 3:41 pm
$
0
0
Problem

You find the following entry in the SharePoint 2010 Central Administration Review problems andsolutions listing:

TitleThe timer service failed to recycle.
Severity2 - Warning
CategoryPerformance
ExplanationThe last attempt to recycle the timer service failed as have most of the other attempts during the past week. Recycling typically fails because other timer jobs are running when the recycle is scheduled. To view which jobs blocked the recycle view the history for the recycle job and click on the failed status link for more information. The error message for the failed job entry will contain a list of jobs that were still running. The history for the recycle job can be found at: [path to timer job history for the associated timer job]
RemedyChange the schedule for the timer recycle job so that it does not conflict with other long-running timer jobs. This can be done from the central administration site at [path to timer job history for the associated timer job].  For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142615".
Failing Servers[server name list]
Failing ServicesSPTimerService (SPTimerV4)
Rule SettingsView
 
Troubleshooting
  1. Navigate to the timer job history and see the list of instances that failed. 
  2. Clicking the Failed status link, the following error message is seen: The timer service was not recycled because the following jobs were still running: Microsoft SharePoint Foundation Usage Data Import.
  3. CA > Monitoring > Timer Job Status, Job Definition: Timer Service Recycle, View: Job Definition
    1. Scheduled to run daily @ 6PM on all farm servers
    2. Duration : 00:10:30.
  4. CA > Monitoring > Timer Job Status, Job Definition: Microsoft SharePoint Foundation Usage Data Import, View: Job Definition
    1. Scheduled to run every 30 minutes on all farm servers
    2. Duration: varies between 6 and 9 hours
    3. Progress has been stuck at 0% for all farm servers for many hours.
    4. Reviewing history: when first started, completed in 2-3 hours.  Now, two weeks later, completes in 6-9 hours.  Steady increases in duration logged over this period.
Solution
  1. At next maintenance window, bounced servers (for other maintenance as well).
  2. Durations had reached 11+ hours for Microsoft SharePoint Foundation Usage Data Import jobs on all servers.
  3. Reviewed job history for Microsoft SharePoint Foundation Usage Data Import:
    1. Durations dropped from over 11 hours down to minutes.
      1. Application Server: few minutes
      2. WFE1: several minutes
      3. WFE2: 10+ minutes.
    2. Difference between WFEs is interesting.  Will need to research this.
  4. Manually started Timer Service Recycle job
  5. Checked Timer Service Recycle job history several hours later:
    1. Succeeded for all servers.
  6. Reopened issue, and then clicked Reanalyze Now.
  7. Checked report a few minutes later:
    1. Issue gone.
This is only a temporary solution until I can get the machines patched, which, according to one of the references below, is one solution to this problem.

References

    ↧
    ↧

    Windows 7: Error event 2: Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188

    January 20, 2014, 9:47 am
    $
    0
    0
    Problem

    The following error appears in the System event log:


    Log Name:      Microsoft-Windows-Kernel-EventTracing/Admin
    Source:        Microsoft-Windows-Kernel-EventTracing
    Date:          [date/time]
    Event ID:      3
    Task Category: Session
    Level:         Error
    Keywords:      Session
    User:          SYSTEM
    Computer:      Main
    Description:
    Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
        <EventID>3</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>2</Task>
        <Opcode>14</Opcode>
        <Keywords>0x8000000000000010</Keywords>
        <TimeCreated SystemTime="date" />
        <EventRecordID>1778</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="176" />
        <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
        <Computer>Main</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="SessionName">Circular Kernel Context Logger</Data>
        <Data Name="FileName">C:\Windows\system32\WDI\LogFiles\BootCKCL.etl</Data>
        <Data Name="ErrorCode">3221225864</Data>
        <Data Name="LoggingMode">128</Data>
      </EventData>
    </Event>

    Troubleshooting
    1. Ran Err.exe to view the error code text.
    2. Launched Computer Management and navigated to: Performance > Data Collector Sets > Startup Event Trace Sessions.
    3. Right-clicked Circular Kernel Context Logger.
    4.   Checked File tab to change file options, but found options disabled:
    5. Searched Registry to find appropriate key that controls log file size, as suggested by this reference, but found not one but several keys (through search for "Circular Kernel Context Logger") having this property:  
      HKLM\SYSTEM\ControlSet001\Control\WMI\Autologger\Circular Kernel Context Logger
      HKLM\SYSTEM\ControlSet002\Control\WMI\Autologger\Circular Kernel Context Logger
      HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Circular Kernel Context Logger

      so, uncertain which to adjust.
    My Solution
     
    Disable Circular Kernel Context Logger.  Given that this workstation was not critical, disabling this logging seemed the most practical approach.

    References
    ↧

    Windows 7: Error 7038: The nvUpdatusService service was unable to log on as .\UpdatusUser

    January 20, 2014, 10:19 am
    $
    0
    0
    Problem

    The following error events occurs in the Windows 7 System log:

    Log Name:      System
    Source:        Service Control Manager
    Date:          [date/time]
    Event ID:      7000
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Main
    Description:
    The NVIDIA Update Service Daemon service failed to start due to the following error: 
    The service did not start due to a logon failure.
    Event Xml:
    ...

    Log Name:      System
    Source:        Service Control Manager
    Date:          [date/time]
    Event ID:      7038
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Main
    Description:
    The nvUpdatusService service was unable to log on as .\UpdatusUser with the currently configured password due to the following error: 
    Logon failure: the specified account password has expired.
    To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).
    Event Xml:
    ...

    Solution
    1. Start Services.msc.
    2. Scroll down to NVIDIA Update Service Daemon.
    3. Double-click it.
    4. Select the Logon tab.
    5. Select the option: Log on as: Local System Account.
    6. Select the General tab.
    7. Click Start.  A prompt will appear.
    8. Click OK, and then click OK again.
    References
    ↧

    SharePoint 2010: Provision the Web Analytics Service Application

    January 21, 2014, 4:33 pm
    $
    0
    0
    Introduction

    This posting presents the steps for provisioning a SharePoint 2010 farm's Web Analytics service application.

    Procedure
    1. Log into Central Administration under an administrator account
    2. Navigate to; CA > Application Management > Manage Service Applications.
    3. On the Service Applications ribbon, click New, and then click Web Analytics ServiceApplication.
    4. Enter the appropriate information for these properties:
      1. Name
      2. Application Pool
      3. Application Pool Security Account
      4. Database Server
      5. Staging Database Name
      6. Reporting Database Name
      7. Data Retention Period
    5. Click OK.
    6. In Central Administration, navigate to: CA > System Settings > Services on Server.
    7. From the Server dropdown, select the farm Server on which you want to run the Web Analytics Web and Web Analytics Data processing Services.
    8. Start these services (Order is unimportant).
    9. In Central Administration, navigate to: CA > Monitoring > Usage Data Collection Settings
    10. Configure options as desired.
    11. In Central Administration, navigate to: CA > Monitoring > Configure diagnostic logging
    12. Configure options as desired.
    References
    ↧
    Viewing all 388 articles
    Browse latest View live
    Search
    <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>