In my IIS log I see many instances of sc-bytes=0.
The time-taken for these entries are generally higher than average.
I can see various values of sc-win32-status like 64, 22, 121, 1236 etc.
Most of them have sc-status 200. Few have sc-win32-status 400.
Now I want to analyse each situation to figure out what happened in IIS.
But this MSDN site gave only the error name and not a detail about when they can occur.
I found a good article here which gave a good scenario description for sc-win32-status = 64 and sc-status = 200 with high time-taken.
I wanted a similar explanation for all sc-win32-status.
Is there any site which gives details about scenario for sc-win32-status codes?
Else can anybody explain when do we get following values for sc-win32-status:
64, 22, 121, 1236.
The IIS Server status codes that you find in the logs are informational and are intended to provide what went wrong in certain requests/responses not why. So when you see an error code like 1326 that simply means that the username and password are not correct etc.
If you want to dig deeper and see why something happens in the background, tools like Debug Diagnostic Tool and Debugging Tools for Windows can help you out to perform analysis.
Related
I am trying to pull over end-of-day share prices going back in time. The code below provides exactly what I need but it appears that that the year/month/day parameters do not work.
import requests
params={'q': 'NASDAQ:AAPL', 'expd': 10, 'expm': 3, 'expy': 2018, 'output': 'json'}
response = requests.get('https://finance.google.com/finance', params=params, allow_redirects=False, timeout=10.0)
print(response.content)
The closing price for this is "l" : "178.65" which is the most recent closing price (15 March) and not for 10 March as specified. I am assuming I cannot rely on this service as it is no longer supported by Google but would be good if someone can confirm if I am correct around the dates not working or if I am missing something.
Well, up until this morning this used to work:
http://finance.google.com/finance/historical?q=NASDAQ:msft&output=csv&startdate=Mar+15%2c+2018&enddate=Mar+15%2c+2018
I asked two other people to confirm on different ISPs and we all get the same error message:
We're sorry... but your computer or network may be sending automated queries. To protect our users, we can't process your request enter code here`right now. See Google Help for more information.
same here:
https://finance.google.com/finance/historical?q=AAPL&output=csv
it looks like google close finance api or change path.
This URL still works:
https://finance.google.co.uk/bctzjpnsun/historical?q=NASDAQ:msft&output=csv&startdate=Mar+15%2c+2018&enddate=Mar+15%2c+2018
I recommend you to make a copy of the data ASAP though, because Google will probably close this other link soon.
I'm trying to set X-Delete-After and X-Delete-At to a file i'm uploading.
So i tired :
FileMetaData.Add("X-Delete-After", "30");
cloudFilesProvider.UpdateObjectMetadata(inStrContainerID, strDesFileName, FileMetaData);
but the header did not get recognized.
is that the right approach?
Edit: I'm trying to use ICloudFilesMetadataProcessor.ProcessMetadata, but really have no clue how to and am not able to find any documentation.
In the current release of the SDK, you can include the X-Delete-After or X-Delete-At value in the headers argument to the following calls:
IObjectStorageProvider.CreateObject
IObjectStorageProvider.CreateObjectFromFile
Currently there is no way in the SDK to change the value of this header after the file has already been uploaded (e.g. using UpdateObjectMetadata as you suggest in the question would set the values X-Object-Meta-X-Delete-After or X-Object-Meta-X-Delete-After, which is not correct).
Here is a related issue on GitHub:
#167: How to assign version folder
Gopstar --
EDITED:
After more investigation; I set the X-Delete-After to 1500 and the code worked. Sort of. When viewing the file header information via the dashboard, the X-Delete-At was set.
However, the result was correct; the X-Delete-At was equal to what would be 1500 seconds from the time I set it.
Original reply:
I played around; if you set the value higher (for example, I tried X-Delete-After = 3000) it will work.
I do NOT know the lowest number acceptable, but I'm sure someone will chime in with the number.
Hope this give SOME help.
In cognos 10.2 i am not getting SecureErrorID with time stamp (which is pretty usefull to search errors in detail in report servers log)in error meassage in cognos report failure message, earlier when we used to use cognos 8 we used to get that term as an error message when report fails.
Anything we missed ? please suggest.
There is a capability setting for this:
Security/Capabilities/Detailed Errors.
You control who does or doesn't get the full error there.
I'm working on a Windows Store app and I'm getting a WinRT error that doesn't really give me any information so I would like to know how to understand these sorts of errors.
Basically I get the error on the following line which is called inside OnPointerPressed:
m_gestureRecognizer->ProcessDownEvent(args->GetCurrentPoint(nullptr));
The error is:
First-chance exception at 0x76F54B32 (KernelBase.dll) in DXAML2.exe: 0x40080201: WinRT originate error (parameters: 0x80070057, 0x00000044, 0x03CEE72C).
This error didn't used to appear, the only thing I've changed is that this line is now wrapped in an if clause which tests if the current pointer's PointerId is the same as one I've stored just using == such as:
if(args->GetCurrentPoint(nullptr)->PointerId == m_UIPointerID)
I have no idea why this has started happening.
So my question is in two parts:
More generally, how do I understand what an error such as the above means?
And does anyone know this error has suddenly started happening now that I check the pointerId?
Thanks for your time.
P.S. I guess another thing that has changed is that there will already be 2 pointers on the screen (the one that gets pushed into this GestureRecognizer) as well as another one, hence the PointerId check.
"How to Decipher such an error"...
For any WinRT originate error, you can take the third address in the parameters list (in your example, 0x03CEE72C), and find a description of your error in the memory window.
While debugging, break when your error is thrown and open the memory window via Debug -> Windows -> Memory -> Memory 1
Copy and paste the address to get your "easy-to-find" error message.
As Raman said - it's good to look up the hex values shown. The first one is the memory location which won't tell you much without the symbols/source, which in this case is reported directly by Windows. Perhaps the public symbols can shed some more light on where the error came from, but the error code lookups are more helpful.
If you Bing for 0x80070057 you will find an MSDN article on Common HRESULT Values which lists
E_INVALIDARG : One or more arguments are not valid : 0x80070057
It doesn't give you all the details of course, so you're off to theorize. Perhaps you can only call args->GetCurrentPoint(nullptr) once and you should store/reuse the value? Maybe gesture recognizer is not configured correctly? Maybe the app window is not visible at the time the exception is thrown or the thread is wrong. Maybe some expected calls to gesture recognizer were missed due to filtering those out with these "if" statements.
I have a rsyslog daemon running on a server receiving and aggregating messages from a number of other servers. Occasionally, I see line written which looks like the start of a message, an ellipsis(...), and the end of another, different, message.
It doesn't appear to have anything to do with the length of the message, as longer messages get through with out problems.
I have looked through the rsyslog doco without success and searching google for ... is not useful. Have I just missed something in the doco, or is this a bug?
The elipsis is actually coming from the log4j syslog appender implementation. If the line is "too long" it will be truncated and an elipsis will be written instead.