Category Archives: Annoyances

Visual Studio VS 2010 not stopping at breakpoints

Ever wondered why suddenly you cannot debug because the compiler isnt breaking on your breakpoints.

There are several reasons for this.

make sure that.
1. Your project is compiling when you begin debugging (check this in build > configuration manager)
2. Ensure your projects are compiling in debug mode not release (check this in build >configuration manager)
3. In the Webconfig ensure you are in debug mode

4. The (project properties > startup options > debuggers has the ASP.NET checkbox checked)
5. Delete all pdb files in your bin folder
6. Ensure every project referenced is set to build under (build > configuration manager)
7. Do a full clean and rebuild. (build > clean solution) (build > rebuild solution)

Finally and this is the one that caught me out
8. Check you are not setting a cookie cache timeout of positive time, I was expiring my page after 1 day. The best way to check this is to load a page in debug, knowing your break point will not be stopped at. Once the page is fully loaded hit ctrl F5 to force full reload of the page. If your breakpoint is stopped at then you know its a cache problem.

ASP.NET Master Page Nested inheritance

I seem to be asked this a lot so i thought i would mention this online so hopefully people will no longer ask me, they’ll find the answer when they ask google

You are trying to inherit from a masterpage and you recieve the following error

the page has one or more < asp:content> that do not correspond with < asp:ContentPlaceHolder> controls in masterpage

Script tags are the culprit around 80% of the time. For some reason the visual studio designer doesnt like not fully closing your script tags at design time.

Change all of you script tags from this

< script type="text/javascript" src="js/myjs.js" /> 

correcting it to this:

< script type="text/javascript" src="js/myjs.js" ><  /script>

Any you should be good to go.

Error 1310 Config.msi verify access

If you recieve the following error when trying to install or uninstall windows applications

Error 1310. Error writing to file: C:\Config.Msi\*******.rbf. System error 5. Verify that you have access to that directory.

You can try and resolve this by re registering windows installer

Open a command prompt Start > run > “cmd”

msiexec /unreg
msiexec /regserver

If this doesnt solve your problem try running your installer from the root of the C drive as an administrator in various compatibility modes.

Tree ms dos command

ever needed to print a tree structure of a folder location, only to realise that you cannot see it all because the tree command doesnt have enough buffer space.

Well just tell tree to output the tree to a file like this

open a command prompt, then paste

tree c:\users /a > “%temp%\t1.txt” & start notepad “%temp%\t1.txt”

change accordingly

MS Outlook Error when opening

If you recieve this error when you try to open your Microsoft Outloo client

cannot start microsoft outlook cannot open the outlook window

open a run command “Start > Run” and type this

outlook.exe /resetnavpane

Should fix most errors
Failing that try these references for outlook switches

http://www.petri.co.il/outlook_2003_command_line_switches.htm
http://www.techgalaxy.net/Docs/Exchange/OL2003_switches.htm
http://office.microsoft.com/en-us/outlook-help/command-line-switches-for-microsoft-office-outlook-2007-HP001218589.aspx

Symantec Antivirus DWHxxxx.tmp Bogus Trojan Horse

Recently one of my users had thousdands and thousands of files in the quarantine
All of them aparently trojan horse risks
All the files began with DWH ending with .tmp
This is infact symantec live update wizard DWHWIZRD.EXE trying to download updates available for the symantec application group rather than obtain the latest virus update list.

In doing so the real time scanner Rtvscan.exe identifies the temp file as a trojan, so depending on the rules in the risk settings will depend on what should happen when risks are found, it either deletes the file or quarantines it, and low and behold the update wizard starts to download the file again.

To resolve the issue (this time), login as an administrator of sorts be it domain or local. Locate the symantec liveupdate folder typically %system%\progam files\symantec\liveupdate and run the LUALL.exe
This will kick off the live update manually, follow the wizard steps until its complete then reboot.

This will likely happen again in the future until symantec either come up with a solution in one of the updates.

Note: this only appears to happen to users that are not part of the “local admin” group of the pc in question.