Archive for category Computers
This error had me “scratching my head” at work this week. I was trying to run a scheduled task which performing some bench marking testing of my parallel load using SqlBulkCopy implementation. I thought I had everything set up correctly, but was getting this error. The “job” was just crashing leaving not a trace, apart from the error code in the Task Scheduler.
I had a network drive mapping as the path to the executable which was to be run (H:\…). This appears to be a big “No No” with scheduled tasks. I also tried using a UNC name to the executable but that did not work either.
Although, this error code is not in the file, WinError.h. The WinError.h file is a very good source of explanations (quick hints) for some errors. Blow is an example of one of the entries in the file. Being able to get just a hint as what the error code is can often be enough to star the process of solving it.
// // MessageId: SPAPI_E_NO_DEVICE_ICON // // MessageText: // // There is no icon that represents this device or device type. // #define SPAPI_E_NO_DEVICE_ICON _HRESULT_TYPEDEF_(0x800F0229L)
The WinError.h file is located at C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include . The file is a C/C++ header file which gets installed when you have C/C++ installed with Visual Studio. or the Windows SDK. The file Windows SDK is available as a separate download and install from MSDN Windows SDK (there are links to downloaded and install the SDK on this page).
This site had a very short explanation for the error code. Something similar content of the WinError.h file. This was enough to get on the right track to solving this problem. DB Security – Win 32 Error Codes.
Copy the contents of .Net build target output from the network onto the C: drive. This scheduled task then worked perfectly.
Simple when you know what the problem is, a real mystery when you don’t.
I wish, that the dialog which is setting up the action of the scheduled task, gave some warning about this potential problem.
Trying to open a compiled help file (chm) which I downloaded from the MSDN site, get the following error:
Windows 7 is being a bit overprotective. Although I say yes I want to open the file:
It may be a useful feature, for some people. It may be my work’s network which has the security levels cranked up to a very high level. For me it is a right pain. Particularly, when I’ve already said yes to one thing only to find I need to do something more.
I have been writing an “Issues and Discussion Paper” at work, for the last week. This has meant I have spent a lot of time working in Word, mainly the outline view.
In drafting the paper I needed to inject some text from some preceding document into the report. To achieve a “neat” presentation for the quoted text, I decided to use the Text Box object. Well, this is where the “fun” (fun only if you are a masochist) started.
Why I use the Outline View
The outline feature of Word is something which I find invaluable. The outline feature of work is invaluable for structuring reports (in my opinion). The ability to start out with a broad outline, refine it by adding new elements, within the document’s hierarchy is invaluable. The other part of the outline which I use frequently is the ability to shuffle part of the document, picking up the heading, and all of the body text below it.
Sometime soon I post on this blog how to get the outline hierarchical numbering working as well. This is not simple to get working, but if you know how does a very good job of showing the structure of the document.
The following is the Word ribbon with the Insert tab selected. The Text Box is then last option shown in the image, there are other things after it, so don’t think it is the last thing on the list.
“Fun” With the Text Box
- The text box does not show up in the outline view. Not a big problem, but indicative of the fact that these are “graphical” objects which are being “massaged” into the text of a Word document.
- These are graphical object. This means that they come with an anchor symbol (see the graphic). You may need to set the Word Options to see all of the characters (which will then show the anchor, and the paragraph mark)
I had the text boxes in my document “dancing” all over the place. In the print layout view, they could turn up on one page, or all on another page, or disappear altogether. This “behaviour” was exacerbated when I put more text into the document, above where the text boxes where (or should have been) located.
The way I managed to get the text boxes staying where I wanted them, rather than were they wander to wander to, was to insert page breaks into the document. This effectively “nailed” each text box, and the associated text onto the one page. This stopped the text boxes wandering off.
The “Page Break” is located on the Insert tab of the Word ribbon.
Text boxes in Word are useful. Having developed this “trick” for keeping them “tied down” to a page, I think that I will use them more often in the “stuff” I write.
I hope this saves someone else, the “aggravation” of having these little things going for a wander in your Word document.