14 KiB
Fehler
Dienstag, 23. Juli 2019
11:12
Chrome :
{width="9.125in" height="6.197916666666667in"}
Erfasster Bildschirmausschnitt: 24.07.2019 11:54
Whats New Darstellungsfehler :
{width="8.0in" height="2.5in"}
Erfasster Bildschirmausschnitt: 23.07.2019 11:13
{width="16.21875in" height="5.21875in"}
Erfasster Bildschirmausschnitt: 23.07.2019 13:51
{width="13.875in" height="2.9166666666666665in"}
Erfasster Bildschirmausschnitt: 23.07.2019 13:51
{width="8.520833333333334in" height="2.6145833333333335in"}
Erfasster Bildschirmausschnitt: 23.07.2019 13:52
weil "Intranetsites in Kompatibilitätsansicht anzeigen" aktiviert ist
Im Haus klären
SPP neue SC hinzufügen :
Wizdom installiert dann auf Wizdom geklickt :
The operation has timed out
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The operation has timed out
Source Error:
| An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
|---|
Stack Trace:
| [WebException: The operation has timed out] System.Net.HttpWebRequest.GetResponse() +1694 Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute() +49 Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb) +326 Microsoft.SharePoint.Client.ClientContext.ExecuteQuery() +609 Wizdom365.BLL.Extensions.SharePoint.ClientContextExtensions.Retry(Action func, Int32 retryCount, Int32 delay) +506 GUI.Web.Base.Pages.Wizdom365.Page_Load(Object sender, EventArgs e) +2316 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +154 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4082 |
|---|
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3282.0
Vorhandene SC können weiterhin auf Wizdom zugreifen.
Editor Symbole :
{width="14.447916666666666in" height="4.041666666666667in"}
Erfasster BildschirmaussAuf beiden Servernchnitt: 08.08.2019 14:10
{width="14.84375in" height="2.9583333333333335in"}
Erfasster Bildschirmausschnitt: 11.10.2019 15:13
{width="5.78125in" height="1.96875in"}
Erfasster Bildschirmausschnitt: 15.10.2019 10:42
{width="14.885416666666666in" height="3.7395833333333335in"}
Erfasster Bildschirmausschnitt: 14.11.2019 13:39
{width="5.552083333333333in" height="2.7083333333333335in"}
Erfasster Bildschirmausschnitt: 14.11.2019 13:40
$json | ? { $_.Catalog -eq 1 } | % {
$appId = $_.ID;
Write-Host -foreground Yellow "Title: $($_.Title)";
Write-Host -foreground Yellow "AppID: $appId";
}
Wizdom SPQ :
| [CryptographicException: Invalid provider type specified. ] System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer) +5539321 System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle) +93 System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() +135 System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32 dwKeySize, CspParameters parameters, Boolean useDefaultKeySize) +199 System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey() +229 System.IdentityModel.Tokens.X509AsymmetricSecurityKey.get_PrivateKey() +179 System.IdentityModel.Tokens.X509AsymmetricSecurityKey.GetAsymmetricAlgorithm(String algorithm, Boolean privateKey) +30 Microsoft.IdentityModel.S2S.Tokens.X509AsymmetricSignatureProvider..ctor(X509AsymmetricSecurityKey x509Key) +52 Microsoft.IdentityModel.S2S.Tokens.SignatureProvider.Create(SigningCredentials signingCredentials) +122 Microsoft.IdentityModel.S2S.Tokens.JsonWebSecurityTokenHandler.Sign(String signingInput, SigningCredentials signingCredentials) +57 Microsoft.IdentityModel.S2S.Tokens.JsonWebSecurityTokenHandler.WriteTokenAsString(SecurityToken token) +389 Wizdom365.BLL.Factories.SharepointContextV3.TokenHelper.IssueToken(String sourceApplication, String issuerApplication, String sourceRealm, String targetApplication, String targetRealm, String targetApplicationHostName, Boolean trustedForDelegation, IEnumerable`1 claims, Boolean appOnly) +708 Wizdom365.BLL.Factories.SharepointContextV3.TokenHelper.GetS2SAccessTokenWithClaims(String targetApplicationHostName, String targetRealm, IEnumerable`1 claims) +98 Wizdom365.BLL.Factories.SharepointContextV3.SharePointHighTrustContext.RenewAccessTokenIfNeeded(Tuple`2& accessToken, Func`1 tokenRenewalHandler) +188 Wizdom365.BLL.Factories.SharepointContextV3.SharePointHighTrustContext.get_UserAccessTokenForSPHost() +71 Wizdom365.BLL.Factories.SharepointContextV3.SharePointContext.CreateUserClientContextForSPHost() +19 GUI.Web.Base.Pages.Wizdom365.Page_Load(Object sender, EventArgs e) +2316 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +154 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4082 |
|---|
Auf dem Wizdom Server:
correlationToken": "467cd8c3-e72f-4c4f-9126-700f3d63ce6a"
Starting new session: ph0khp3jgpp1vmakthfajtf4
29.06.2020 12:17Es scheint immer eine bestimmte Abfrage auf dbo.Cache der Wizdom-DB zu sein
SELECT TOP (1)
[Extent1].[Modul] AS [Modul],
[Extent1].[Key] AS [Key],
[Extent1].[Value] AS [Value],
[Extent1].[Inserted] AS [Inserted],
[Extent1].[Expire] AS [Expire],
[Extent1].[Type] AS [Type]
FROM [dbo].[Cache] AS [Extent1]
WHERE [Extent1].[Key] = @p__linq__0
(Get-ChildItem d:\wizdom-spp -recurse | Sort-Object length -descending | select-object -first 32 | measure-object -property length -sum).sum /1gb
Get-ChildItem d:\wizdom-spp -recurse | Sort-Object length -descending | select-object -first 32