Jump to content

Troubleshooting Sending Self Destruct Messages


support
 Share

Recommended Posts

If you are having issues when trying to send Self Destruct Messages, please refer to the following questions/suggestions, and please provide this feedback to Click Studios when logging a support call:

  • Please provide a screenshot of the error you are seeing
  • Are you using the Self Destruct Message web site which comes embedded with your normal Passwordstate web site, or have you installed this site separately?
  • With the error message you see, is the URL being reported accurate? If you are using the embedded site, the URL used is the Base URL field you can see on the screen Administration -> System Settings -> Miscellaneous tab. If you have installed the site separately, then it's the URL you have specified on the screenshot below
  • Do you use any Load Balancers or Reverse Proxies in your environment?
  • As per the screenshots below, can you confirm the encryption key is set correctly in the file C:\inetpub\Passwordstate\selfdestruct\web.config – this path will be different if you have installed this site separately

 

destruct1.png

 

destruct2.png

 

Regards

Click Studios

 

Link to comment
Share on other sites

  • 1 month later...

Unfortunately an error has occurred within the Passwordstate web site, for which we apologize for the inconvenience.
 

If Passwordstate is able to communicate with the database, then the error will be logged on the screen Administration -> Passwordstate Administration -> Error Console.
 
If you are unable to view the Error Console screen for any reason, you can ask your Database Administrator to run the following SQL Query, which will show the same data from the Error Console Screen:

USE Passwordstate
SELECT * FROM DebugInfo
 

image.thumb.png.9bae33f4be83185f2d32d9a852a57161.png

 

9/17/2019 12:54:16 PM  General Error  

Invalid viewstate. Client IP: 10.60.73.8 Port: 30700 Referer: https://ofpasstate01pr.vitamix.com:9119/passwords/shared/default.aspx?screenwidth=1473 Path: /passwords/shared/default.aspx User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3891.0 Safari/537.36 Edg/78.0.268.1 ViewState: uyjGkmMGSQmerahcywgnDM1GdXJBxCUkcrakkQu7YlD4S/HRgqeCeywCv45wggkKQObBqLmwMmpJJr6B8WYd1T5i076Q2ko+aBLYCb5eSuiE3VlkoKKiRCsCNUKzFotC9f2AsvYYXXayJ4BViROAU/wNj5lVLcXjM733wSOc+0BEhYXp1iLxeclKpOyaGXtmc2lsKp2x49AvRbbczyZ/1SG/OgzgILF3BMkxclIq/rk+fG6+sjer3rfMMtJWbZC+h9rgo3np3b3LfXkbxLxzVSFyDMoPduumvISoEGMTOi21m8cAIdVMfrvOTamOvjOAcH7LDd5Yoh+e4ZCOGQD/ySlqiJEtBIyKsiL/WA+UylMyhTjL3F8rBRY1SkBmU1cFerZFiUpzxT1y+sANKFxCLsEUTS71ZlN6CzxQPD4dLaDAqxXnc+vpHYddcCV9u6//jzKuisArR0ek5VbFMUN06nrRdoQSZQxWGLU/73uEql8nfa8SCmv39cLwrys8LwL0ivEwaHzc5CTT/3FKMO+7TDdiUQrrA04fsQDmRHkc7IoKtr2vgC25pq4rRHHb8TiOrWSkaJod0uPjdedy/ixXiUsi0bklIhu/e1cTjcBt134D3R+fVr14CgcXOLItK2I15Fdwohc5RPhdvIMaw/Ngi+9GnEyL5Acgd74gcfeJwAuSL9ZGF..., StackTrace =

 

 

  • Are you using the Self Destruct Message web site which comes embedded with your normal Passwordstate web site, or have you installed this site separately? Embedded
  • With the error message you see, is the URL being reported accurate? If you are using the embedded site, the URL used is the Base URL field you can see on the screen Administration -> System Settings -> Miscellaneous tab. If you have installed the site separately, then it's the URL you have specified on the screenshot below. URL Correct
  • Do you use any Load Balancers or Reverse Proxies in your environment? No
  • As per the screenshots below, can you confirm the encryption key is set correctly in the file C:\inetpub\Passwordstate\selfdestruct\web.config – this path will be different if you have installed this site separately. File attached

 

I am now unable to go into settings and check Self destruct setting, I get the following error:

 

The file '/admin/systemsettings/default.aspx' has not been pre-compiled, and cannot be requested., StackTrace = at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Web.config

Link to comment
Share on other sites

After upgrade and reboot, I am able to go through the steps to send self-disctruct message, but get the following error:

 

There was an error communicating with the Self Destruct Message Site on the URL of 'https://ofpasstate01pr.vitamix.com:9119/selfdestruct/'. Please check the logs folder on the Self Destruct Site for more details. Error = The underlying connection was closed: An unexpected error occurred on a send.

 

image.png.c16543244be1e078f7412694dd98bbf8.png

 

If I copy the url from the self-distruct message, https://ofpasstate01pr.vitamix.com:9119/selfdestruct/?id=8fb4bb085f6d4c24946eb175e43a3cc3  I get the following error:

You do not have permission to view this directory or page.

Link to comment
Share on other sites

Hi Eric,


For the previous error of "has not been pre-compiled", that is generally caused by lack of disk space, or a failed upgrade attempt of Passwordstate - just for future reference, in case you see it again at some stage.

If you look in IIS, do you see the 'Selfdestruct' folder configured as an "Application"? If not, then possibly someone missed our post upgrade instructions, and you can follow the KB Article title 'Configure Self Destruct IIS Application' in the User Manual, which you can find under the Help menu in Passwordstate?

Can you let us know if this helps?

Regards

Click Studios

Link to comment
Share on other sites

Hi Eric,

Can you check again that "As per the screenshots below, can you confirm the encryption key is set correctly in the file C:\inetpub\Passwordstate\selfdestruct\web.config – this path will be different if you have installed this site separately" - I assume this matching the encryption key on your System Settings -> Self Destruct Messages?

If you go to the screen Administration -> Error Console, is it reporting any more error data for this? It's odd that we get the message "The underlying connection was closed",  when you've confirmed all the information above is correct - we're not exactly sure what else could cause this.

Regards
Click Studios

Link to comment
Share on other sites

  • 1 year later...

Yes it is. But you probably can see in the eventviewer (application log) which assembly is causing your problem. In our case this showed up:

Exception message: Could not load file or assembly 'Microsoft.EnterpriseManagement.OperationsManager.Apm.DataCollecting.Producers.Mvc.4.0, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Googling showed that this was related to Microsoft Monitoring Agent, but I think other apps can mess with these as well. 

 

It is shown as warning for ASP.NET (eventID 1309)

 

-Stefan

Link to comment
Share on other sites

I am seeing this event once a day:

 

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 3/18/2021 1:13:18 AM 
Event time (UTC): 3/18/2021 5:13:18 AM 
Event ID: 57415b0d8f8d444a828bef60e3222c37 
Event sequence: 9678 
Event occurrence: 1 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/1/ROOT-1-132605178893806099 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\inetpub\wwwroot\ 
    Machine name: OFPASSTATE01PR 
 
Process information: 
    Process ID: 924 
    Process name: w3wp.exe 
    Account name: IIS APPPOOL\DefaultAppPool 
 
Exception information: 
    Exception type: HttpException 
    Exception message: A potentially dangerous Request.Path value was detected from the client (:).
   at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
   at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)

 
 
Request information: 
    Request URL: http://ofpasstate01pr.vitamix.com/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/
    Request path: /api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/ 
    User host address: x.x.x.x 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: IIS APPPOOL\DefaultAppPool 
 
Thread information: 
    Thread ID: 12 
    Thread account name: IIS APPPOOL\DefaultAppPool 
    Is impersonating: False 
    Stack trace:    at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
   at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)
 
 
Custom event details: 
 

Link to comment
Share on other sites

Hi Eric,

 

Generally when we see the error "A potentially dangerous Request.Path value was detected from the client (:)", this means that either someone is doing a deliberate penetration test against your Passwordstate instance, or you have a scanning tool looking for vulnerabilities.

 

These errors are created by our software to protect you from malicious attacks.  We do not believe this would be an intruder on your web server, because if they had enough access on it to run some sort of tool, they wouldn’t be trying to scan pages that don’t even exist.

 

If you do not think the above information is correct, please let us know and we can continue to investigate.

 

Regards,

Support.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...