This is a blog on all things Microsoft that I could not find the answers for when I looked. I hope that by my documenting the fix, I save you the hassle!
Wednesday, October 03, 2007
Error Code: 500 Internal Server Error. The network logon failed. (1790)
The problem is that the firewall access rule for this web site in ISA Server is forwarding the requests to an internal server on a port that it is not listening on. For example you connect to https://server.example.com and the ISA Server forwards this request to http://internalsrv. On the Bridging tab check that the mentioned port(s) are actually working on the internal server. For example if you are listening in ISA Server on 443 for a SSL connection and the SSL/HTTPS port is ticked make sure that the port is 443, and that the web server internally is listening on 443. If its another number make sure that it is meant to be the other number and not really 443 or not ticked at all. Ditto for the HTTP port, which is 80 by default.
Friday, September 21, 2007
Can't Update Media Player Library on Windows SmartPhone
To fix:
Delete the MSMETADATA folder in the root of the Storage Card.
If using File Explorer on your device note that it's not visible by default. You have to select the "Show All Files" option in File Explorer. Once deleted rebuild your library using Media Player, and see if that helps.
Tuesday, June 19, 2007
Fixing Error 1324.The path xxx contains an invalid character.
When installing software I have now seen a number of times the following error "Error 1324.The path My Documents contains an invalid character.". My Documents could be replaced by a number of other special folders, and I have seen this issue on Windows XP and Windows Vista.
The problem seems to stem from having UNC paths for folders (i.e. \\server\share\user\my documents). So, to fix the issue you need to temporarily change the path to a local path and change it back after installation. These steps will help (based on Vista, but XP is similar):
- Click Start
- Right-click Documents (or Pictures etc.)
- Choose Properties
- Make a note of the path currently used
- Change path to the Default by clicking Restore Default button
- Click OK
- If prompted about creating folder say Yes
- When prompted about moving all your files say no (you are going to move the folder back shortly) and then wait a bit - this might take some time.
- Install your application
- Repeat above instructions to move the folder back again, but this time do move the files. This will merge changes to the folder back to your actual folder.
Sunday, July 16, 2006
Setting MP3 ID Tags with CDDBControl.dll
Using tools from Sysinternals did not give me any additional information on why this restriction was true (as the file I was changing had got full control for the limited user that runs the script) so I added the DLL to Component Services as described below to solve the problem.
- Create a new user account with administrative permissions on the local machine. Give this account a very complex password and require that the password never expires.
- Login as this account and start Component Services (in the Administrative Tools area of Control Panel)
- Expand the Component Services tree until you get to COM+ Applications and right-click this node of the tree
- Choose New Application, Create an empty application and provide a name such as ID3Tag for the application. Keep the default of Server Application set.
- On the Set Application Identity page choose This User and enter the details for the current user account. It is important that you select this option and do not leave the default value of Interactive User set.
- Once the component is created, right-click the component and select the Pooling & Recycling tab. Set 1 minute for the Expiration Timeout value (unless your script takes longer to run) and click OK.
- Expand Component Services so that the contents of Components under your component are visible (this area will currently be empty)
- If you have already registered the control with regsvr32 then you need to unregister it using regsvr32 -u "path\CDDBControl.dll"
- Find the folder in which you have copied CDDBControl.dll and drag the dll into the Components container in Component Services
- You will get an error about some components not being able to be installed. You can click OK at this point.
You can now run your script as a limited user and when you call the id3.SaveToFile function the script will not fail with error 0x82fc100c
Saturday, May 06, 2006
Virtual PC's Crashing With IntelPPM.sys and Processor.sys
The blue-screen is due to the virtual machine running on an AMD K8 or Centrino platform and the above device driver attempting a unsupported command that was supported on the platform that the virtual machine was originally created under. You can disable these drivers without issue in the virtual machine - just you cannot login to disable them!
So you need to use Safe Mode. Press the F8 key repeatedly as the virtual machine boots and then choose Safe Mode from the on-screen menu. Once you have logged in run these two commands from a command prompt (note that where the spaces are is important):
sc config processor start= disabled
sc config intelppm start= disabled
You should get a SUCCESS message returned. Once you do you can shutdown the virtual machine (and commit changes if you are have undo disks enabled) and then start the machine up normally.
This problem has been fixed under Virtual Server 2005 R2, but is still an issue with Virtual PC 2004 and Virtual Server 2005.
Thursday, February 23, 2006
Adding Routes Using CMAK
Error 1: Connect action to update your routing table failed (80070057) - shown in the VPN client
Error 2: ErrorCode = -2147024809 ErrorSource = to update your routing table - recorded in the VPN log file
The reason! It was because I had entered an incorrect routing record in the text file. So to get this right, add the routes manually when connected and make sure they work, and then duplicate these entries in the text file. If the routes cannot be added on the command line then the VPN connection will fail with the above error message.
Monday, February 13, 2006
P1 and P2 Headers in SMTP
P1 = the value on the MAIL FROM command of the SMTP connection (the message envelope) as defined in RFC 821.
P2 = the email address in the message body as defined in RFC 822. These include the FROM, REPLY TO and SENDER fields
For example, the following SMTP command sequence describes where P1 and P2 are used:
HELO server
MAIL FROM this_is@my_p1_address.com
RCPT TO: recipient@domain.com
DATA
FROM: this_is@my_p2_address.com
TO: recipient@domain.com
SUBJECT: This is a blog on P1 and P2
This is the text of the message
.
The MAIL FROM value should be your email address, but it does not have to be (ie one of the reasons why spam is so prevalent)
The FROM: header should match this, but this value is what is displayed in the email in Outlook (and other clients). The P1 address is used for routing and not display.
If the connection to an Exchange Server is anonymous then the P2 address will contain the display name and the email address, but if it is an authenticated connection then the P2 email address will be resolved to the value in the address book and this value will be displayed.