You get that error when the authentication bundles haven't started yet. In some cases this is just a matter of time - the start up may still be progress. If it isn't just time then there are any number of reasons why the authentication bundles might not have started. There are two steps you need to take to troubleshoot the issues:
Look at your error.log during start up and look for exceptions and error messages. These exceptions and error messages will clue you into what the problem is.
If you don't see error messages log into felix and see if you have any bundles that aren't starting and try to manually start them and watch the error logs while you are manually starting them.
Are you sure that the user you are running AEM as has read access to the files? Usually when you see errors like that it's on a Linux/Unix system and someone changed ownership of the files to another users.
If you are running on windows then I don't know - it has to be be some sort of permissions issue however.
Yep, its the same user who has created these files and its running on windows which is exactly the reason why I am wondering how to figure out whats is the issue and how to resolve this !
