EventID: 534. The user has not been granted the requested logon type at this machine

On doing a windows security update I started getting this error in my event log, and none of the users could login to the secure sections of the IIS site using basic authentication. I restarted the server and found out that firewall got enabled itself and locked RDP out as well 🙂 Anyway the server guys sorted out the firewall access issue, however in order to sort out the login issue I had to make changes to the local security policy. The two properties you need to check in Local Policies -> User Rights Assignment are “Access the computer from the network” and “Deny access to this computer from the network”. Make sure that your required group is present in the first policy and excluded from the Deny policy, since Deny policy overwrides all allow policies. So after some effort I was finally able to get everything working again. Hence the conclusion is I have asked my company to get a MAC for me 🙂

500 null, Coldfusion server crash after using CF administrator JVM settings

CF Server 7 Crash with 500 null Error.


OS: Centos Linux 4
CF: CF MX 7 patched and hotfixed to accumalative hot fix 2 released in Feb 2006.

Context :

Yesterday we used the CF Administrator to place a Jar file in the JVM class path, after applying the setting through the CF administrator we restarted the CF Server and all hell broke loose, the CF administration page came up with a 500 null error.
On checking the event logs CFserver.log indicated all sorted of errors like

08/03 09:16:32 user failed to load: coldfusion.CfmServlet
08/03 09:16:32 error
at coldfusion.bootstrap.BootstrapClassLoader.loadClass(BootstrapClassLoader.java:229)
08/03 00:33:05 user failed to load: flex.server.j2ee.filemanager.FileManagerServlet
08/03 00:33:05 error Could not pre-load servlet: CFInternalServlet
08/03 00:33:05 user failed to load: flashgateway.controller.GatewayServlet
08/03 00:33:05 error Could not pre-load servlet: CFFormGateway
08/03 00:33:05 user failed to load: coldfusion.xml.rpc.CFCServlet
08/03 00:33:05 error Could not pre-load servlet: CFCServlet
08/03 00:33:05 user failed to load: flex.server.j2ee.SwfServlet
08/03 00:33:05 error Could not pre-load servlet: CFSwfServlet
08/03 00:33:04 user failed to load: coldfusion.CfmServlet
08/03 00:33:04 error Could not pre-load servlet: CfmServlet
08/03 00:33:04 user failed to load: coldfusion.server.j2ee.CFStartUpServlet
08/03 00:33:04 error Could not pre-load servlet: ColdFusionStartUpServlet
08/03 00:33:04 user failed to load: flex.compiler.MxmlServlet
08/03 00:33:04 error Could not pre-load servlet: CFMxmlServlet
08/03 00:33:04 user failed to load: flex.server.j2ee.cache.CacheFilter
08/03 00:33:04 error Error loading class for Filter CFCacheFilter: Filter is disabled.

In panic state we removed the jar file that we installed and removed its reference from the jvm.config file and restarted the server , but no luck, we compared the jvm.config file with the jvm.config file on another server and found it to be fine.

Then on searching from google we found out that 500 null error can happen due to license file corruption so as instructed we changed the license file with a license file from another running install of CF Server, restarted the server but no luck.

The CF server was hagging up on the startup and although it did show up in the running services but on accessing the CF administrator or any of the CF sites we were getting the null error.

Found few posts on CF forums about this



but no solution other then to reinstall CF


Reinstall CF Server, Did the reinstall and went to CF admin to setup JVM parameters like I always do, but on saving the page for the same 500 null error and the server went down again.

Hence did a full reinstall again, applying all hotfixes and updaters todate, and this time knowing the issue with the JVM admin page did not touch it, and the server seems to be running okay now.


CFMX 7 server on Centos Linux 4 has a bug with the Admin interface of CF for the JVM setting and corrupts the configuration files beyond repair and one has to rebuild the server to get it sorted. So best is to alter the jvm.config manually to get this issue sorted.

Annoying Exchange Issue. Authentication error on Mac Mail using Exchange

Exchange has got loads of issue when it comes it making it work with Mac OS. I created and account a month ago and had to rename it. Although after the rename of the account the user was able to login to the windows client and also use outlook and OWA to login and use email but when the same user tried to login using Mail on Mac it did not work for him. Mac Mail was giving authentication error, on investigating a bit further I came to realise that it was a server issue rather then a client issue.

It turns out the on account rename the alias for the mail account was not changed, so the login name and he alias name for mail account was different, on making them similar I was able to login using Mac Mail. This practice took me almost 3 hours to sort this issue out, so I decided to blog this for any other unfortunate ones who bump into this issue. I am just glad that I did not try to back the mail account and delete and recreate it, that would have taken me almost a day to go through all of that.

Old Backup file deletetion issue on SQL Server maintenance backups

Problems :

I recently came across this issue of SQL Server not deleting backups files older then a specific time. In my SQL Server maintenance plan I had specified to delete backups after a week, but on my installation the backups were not getting deleted.


In order to sort this out I was given various suggestions on the MS news groups, but the one that worked for me was to change the recovery option of the databases from simple to either bulk or full. If you take the properties of a database in SQL Server, and then click the options tab, there are settings for recovery for the database, you need to make sure that they are not selected to simple for all databases otherwise the maintenance plan fails to delete the older files. Other suggetions are listed as under.

Below KB might help:

This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.

1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.

Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from http://www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.

If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).

Finally, inspection of the maintenance plan’s history report might be

Backup and Restore Exchange Server

Back and Restore Exchange store

There are two main ways to backup and restore exchange.

1) Online backup : Done using windows backup utility or any third party utility. There is a Microsoft Exchange server tab in the backup utility, backup tab. expand that to select your computer and then select the First information store, the First Information store should show the Private and Public folder group. Select the First information store to backup everything below it, make sure that in settings Backup type Normal is selected. This will backup the exchange store, this might take a long time depending on the site of mailboxes.
In order to restore the back , select the restore tab and then left click on the file tree and add the catalog file that was backed up, this will show the full tree of backed up files, selected the store to be restored, the store can be restored to an existing location or to a new server.

2) Offline backup : For this one takes the file backup of the database for exchange. This cannot be done when the Exchange store is mounted, one first needs to unmount the exchange store and then manually copy the database files to an alternate location.


“Coldfusion MX” to be or not to be ?

Seems Server crashes is something that coldfusion has to live with for ever. During my 2 years or CF Server administration CF Sever has never behaved the way it should , it always finds ways to crash, and worst thing is that its so hard to debug the cause of the server crash, the CF logs generally not much help when it comes to server crashes. After running smoothly for few months our CF Server on windows 2003 has started to crash, previously it was on linux , but now its happening on windows also. It seems to have occured at the same time as the release of a new version of a CF application. So it might be to do with code, but there is no way to finding that out, so for now its hit and trial. My suggestion for new commers to web development is if they want to reduce cost and maintenance time stay away from CF, use PHP nothing matches PHP with respect to speed, stability and being cross platform, if I have to develop a website for myself it will be php for sure.

Here is one forums post to just site and wonder.