Solved: “The username you entered could not be found” when connecting to network share on windows O.S.

If you try to connect to a network share you may receive the error:

“\\name of computer is not accessible. You might not have permission
to use the network resource. Contact the administrator of the server
to find out if you have access permissions”

And the message: “The username you entered could not be found.”

You also have the rights to access the share, no firewall problems, and your user is not locked out or expired.

The solution is to open the command prompt and type:

Control keymgr.dll  

windows vista:

windows 7:

Find the address of the server and delete it from the cached credentials, try to reconnect and .. it should works.

How to inspect Blue Screen Issues or the Blue Screen of Death (BSOD)

Hello, today I’ll show you how to address the terrible Blue Screen on windows systems, this problem i also known as “BSOD Blue Screen Of Death”

Here is a typical BSOD:

The most important info is the first error code (number 1) and, if present, the driver/dll who caused it.

The hexadecimal number following the word "STOP" is called the bug check code or Stop code.

If you read the “Device and Driver Development Tools – Bug Check Codes” you can find the error code and what it means, for example the STOP:50 is a :

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.

The other parameters are specific for the error code, in this example the third parameter identifies a “Write Operation” on Memory.

Now we have two options, the Easy Way and the Hard Way, let’s start from the Easy Way.

Remember to enable the Crash Analysis option using the System Option from the Control Panel , see also this link

The Easy Way- if you need to run

Install this useful application WhoCrashed from Resplendence Software House.

Launch the application on the system where the BSOD appears, download,if asked, the Debugging Symbols from Microsoft and click the “Analyze” button, after some time the app will show you the info about the most suspect dll/driver, here is an example from the SW web site:

Upgrade/Disable/Uninstall it and… the BSOD will disappear.

The hard way – if you need to know the details

Install the “Debugging Tools for Windows”  debugger, configure the Symbols Path with the right string, for example:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Use the “File—>Open Crash Dump” option and load the dump from “%SYSTEMROOT%\minidump”

At the first load you can see this message:

Execute the !analyze –v command, the debugger will analyze the call stack:

Click on the module name link and you will see the path and the details of the faulting module:

Identify the DLL vendor and update his application or uninstall/disable it if no updates are available, the BSOD should disappear from your system.

Hope it helps!

UPDATE #1

How to disable a BSOD driver from windows start

If the BSOD is caused by a driver you need to disable it from loading on windows boot.

Download from sysinternals site the AutoRuns program, execute it and open the Drivers Tab:

Error C1108, "alink.dll" not found on VS2005,Windows 7

After the upgrade from Vista to Windows 7 I started to see some weird errors during the build step of VS2005 VC++ projects, the error was:

"fatal error C1108: unable to find DLL: 'alink.dll'"

Another problem was the crash of mt.exe during the updating of the manifest.

If you have installe the VS2010 beta before the Windows 7 Upgrade, here is the solution to these errors:

Uninstall VS2010 beta
cmd /c "msiexec /x {19BD09BF-3BBD-3663-A5ED-50B6B2B07E42} /qb" 
cmd /c "msiexec /x {1DF6A8F6-5048-323F-8758-DA533CE0F07E} /qb"

These commands will remove the Beta1 4.0 Framework from your machine, and after this all the projects will compile succesfully.

More details on:

http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/a5d827d7-05b4-41b9-9565-e9e4abb12e66

Hope it helps,