User:Ttenbergen: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m testing only |
||
| Line 20: | Line 20: | ||
== Tina is doing some test editing == | == Tina is doing some test editing == | ||
Trying to catch an error to fix our ongoing boot-outs. | Trying to catch an error to fix our ongoing boot-outs. Apparenlty a single quick little edit doesn't do the trick. So, lets ad a whole lotta garbage and wait a few minutes. | ||
I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these | |||
errors. It is odd because the message you see below is indeed | |||
generated by what looks like your IT departments proxy server. Do you | |||
happen to have a screenshot or error message from a different internet connection? | |||
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not | |||
intermittently as it is now. I'm even more certain that it has nothing | |||
to do with the directory structure change, because if that were the | |||
case, the error you would see would have been generated on our server. | |||
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end. | |||
Revision as of 10:52, 10 March 2009
- Also see: Tina Tenbergen
Table Paste Testing
Testing code generated by the macro from here.
The excel file with the macro can be found here.
Green Sheets
File Links
[file://sbghnwfs0102/NSSVOL1/shared/ICU_DATA_COLLECTION/Output a link to the output directory on sbghnwfs0102]
Lowercase
lowercase works so hopefully so do the others... http://en.wikipedia.org/wiki/Help:Parser_function try this
Tina is doing some test editing
Trying to catch an error to fix our ongoing boot-outs. Apparenlty a single quick little edit doesn't do the trick. So, lets ad a whole lotta garbage and wait a few minutes. I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.I'll have a look on our end and see if I can find the source of these errors. It is odd because the message you see below is indeed generated by what looks like your IT departments proxy server. Do you happen to have a screenshot or error message from a different internet connection?
I really dont think it's possible that these issues are caused by the subnet change because if that were the case, the errors should have stopped happening after a certain period of time during which the old DNS records hadn't expired, or produced the error 100% of the time; not intermittently as it is now. I'm even more certain that it has nothing to do with the directory structure change, because if that were the case, the error you would see would have been generated on our server.
The next time you see this error, could you please record the exact time, date, IP address, and screenshot of the computer that is receiving the error and I will try and further investigate the logs on our end.