User profile for Brahim22

It sounds like there might be a configuration issue with your IIS server or Smart Assembly when handling HTTPS requests. Here are a few things to check: 1. **SSL Certificate Configuration**: Ensure that the SSL certificate is correctly configured on your IIS server. Sometimes, an improperly configured SSL certificate can allow some connections (like sending crash reports) but fail on others (like retrieving reports). 2. **Firewall and Network Settings**: Check if there are any firewall or network settings that might be blocking HTTPS traffic specifically for the report retrieval part. Since you can send reports but not retrieve them over HTTPS, it's possible that a specific port or type of request is being filtered or blocked. 3. **Smart Assembly Configuration**: Verify the Smart Assembly settings to ensure that it is correctly configured to handle HTTPS requests. There might be an issue with how Smart Assembly handles SSL/TLS handshakes for downloading reports. 4. **Server Logs**: Examine the IIS logs and any relevant Smart Assembly logs for errors or warnings when you attempt to download the reports. These logs might provide more detailed information on why the connection is timing out. 5. **Mixed Content**: Ensure that there are no mixed content issues where HTTP and HTTPS content are being served simultaneously, causing the HTTPS requests to fail due to security policies. https://nsapp.download/nswhatsapp-3-orange/ 6. **Timeout Settings**: Check the timeout settings on both your IIS server and in Smart Assembly. There might be a discrepancy in how long the server waits before timing out, which could be causing the issue when retrieving reports over HTTPS. By systematically checking these aspects, you should be able to identify and resolve the issue causing the HTTPS connection timeout when retrieving error reports with Smart Assembly. / comments

It sounds like there might be a configuration issue with your IIS server or Smart Assembly when handling HTTPS requests. Here are a few things to check:1. **SSL Certificate Configuration**: Ensure ...

0 votes

This error message definitely sounds frustrating, especially since you're new to SQL Monitor and it's only happening on one specific instance. Here's what's going on: The Error: SQL Monitor is encountering an invalid data point. The "procc.cpu" column, which likely represents processor usage, has a negative value, and SQL Monitor doesn't expect negative CPU usage. Possible Causes: There are a couple of things that could cause this: Bug in Monitoring Script: It's possible there's a bug in the way SQL Monitor is collecting data for this specific instance. SQL Server Issue: On the less likely side, there might be a weird issue with how SQL Server itself is reporting CPU usage for this particular instance. What to Do: Here are some steps to troubleshoot: Check the Script: Look into the specific monitoring script or configuration for this instance in SQL Monitor. See if there's anything related to CPU data collection that might be causing the issue. Compare with Working Instance: Since another instance on the same machine works fine, compare the monitoring setups for both instances. This might help identify any configuration differences that could be causing the problem. Search Online Resources: Search for the specific error message ("Bad Data InvalidDataException column procc.cpu has negative value") related to SQL Monitor and SQL Server 2005. You might find similar cases and solutions from other users. Contact SQL Monitor Support: If nothing else works, consider contacting SQL Monitor's support team directly. They might have specific insights into troubleshooting this error within their software. Hopefully, by following these steps, you can identify the culprit behind the negative CPU value and get your SQL Monitor running smoothly for all your instances! visit https://nsapp.download/ / comments

This error message definitely sounds frustrating, especially since you're new to SQL Monitor and it's only happening on one specific instance. Here's what's going on: The Error: SQL Monitor is en...

0 votes

If you're experiencing File Explorer for pc opening automatically after installing Redgate software on Windows 10, it's likely due to a configuration or compatibility issue. Start by checking if there are any shortcuts or startup entries associated with Redgate that might be triggering this behavior. Navigate to Task Manager (`Ctrl + Shift + Esc`), then review the "Startup" tab to disable any Redgate-related entries temporarily. Additionally, ensure that the software is fully compatible with Windows 10 and that all settings are configured correctly to prevent any conflicts that could lead to unwanted automatic actions like File Explorer launching repeatedly. If these steps don't resolve the issue, considering reinstalling the Redgate software or contacting their support for further assistance may be necessary to troubleshoot and resolve the problem effectively. / comments

If you're experiencing File Explorer for pc opening automatically after installing Redgate software on Windows 10, it's likely due to a configuration or compatibility issue. Start by checking if th...

0 votes

How can we help you today?

Brahim22

Activity overview