సంధ్యావందనము - మంత్ర అర్ధములు

Sandhyavandanam - Meaning of various mantra

సంధ్యావందనము - మంత్ర అర్ధములు

హిందూ సనాతన ధర్మము ప్రకారము ఉపనయనము జరిగిన ప్రతి వ్యక్తి రోజు తప్పక చేయవలసిన కార్యము సన్ధ్యావన్దనము. అలాంటి ముఖ్యమైన కార్యమును ప్రతి నిత్యం చేస్తున్నపుడు ఆ కర్యములోని మంత్రములకు అర్ధములు తెలిసి చేయుట ఎంతో ముఖ్యము. ఎందుకంటే అర్ధం తెలుసుకోకుండా చేసినదానికి అసలు చేయకపోవటానికి పెద్ద తేడా ఏమీ లేదు. గురు ముఖతః సంధ్యావందనము చేయటం నేర్చుకుంటే సాధారణంగా అర్ధం బోధిస్తూనే నేర్పుతారు. కాని ఒకవేళ అర్ధం తెల్సుకోకుండా లేకపోతే సగం సగం తెల్సుకొని చేయవలసి వస్తే పరిస్థితి ఏంటి? అందుకనే నేను సంధ్యావందన మంత్రార్ధములు చెప్పే రెండు పుస్తకాలని చదివి అందులోని భావాన్ని నాకు అర్ధమైనన్థవరకు కలగలిపి ఈ ఫైల్ లో ఉంచాను. మీకు అవసరమైన చో డౌన్లోడ్ చేసుకొని చదవగలరు.

ఇందులో ఏదైనా గొప్పతనం ఉంటే అది ఆ రెండు పుస్తకాలు రచించినవారిదే. ఏవైనా తప్పులు ఉంటే అవి నావిగా భావింపగలరు.

ఫైల్ ని ఈ కింది చోట నుండి డౌన్లోడ్ చేసుకోగలరు.

https://docs.google.com/file/d/0B_3nwxYRiuMuakJwdWRFeHg0RGc/edit?usp=sharing
 

HTTP 500 Internal Server Error–SharePoint 2010 Applications

Among the various HTTP return status codes that we receive, the two most frequent ones are 401s and 500s. While the 401s are more related to authentication and authorization, the 500s are because of problems within IIS. I am listing various things to check and ways to troubleshoot the HTTP 500 errors for IIS web applications in general and SharePoint 2010 applications in particular.

• The first thing you want to check when you receive this error, when you hit the root site of the web application, is the status of the application pool of the website. Is the application pool running?Crashed? Is the application pool properly associated with the web application?
• There is could be a possible 500 server errors in some scenarios based on the load balancer configuration. There are few settings for IIS application pools that that recycle the application pool at preconfigured intervals, by default every day. When the web applications are hit after recycle or the pool dies out the memory, I have learnt that the IIS 7.5 takes some time to WARM UP and if the load balancer’s time out is not configured to be greater than the warm up time, it is going to tell back to the client that there is some error. So make sure you have properly configured those time-outs and if you see such type of issues, just set up a warm job that keeps on pinging the URL of the web application.
• You can see the trace logs in SharePoint 2010, whether there are any assemblies that got knocked out of the assembly. If so, make sure they are added back and reset IIS to get the replaced .dll picked up.
• If you do not see any of these work, Microsoft has given a nice feature with in IIS to trace out the failed requests. Probably this should be used by every single administrator who works on IIS. This is called “Failed Request Tracing Rules” available under IIS section in the Features view of each web site.

1. Enable the Failed Request Tracing logs and configure the location to store the trace logs.
2. After that, double click on the feature to add the trace rules. Click on Add button to add the content source, select All Content. Click Next.
3. Select the status code option and give 500 as the status code. Click Next.
4. Select all the provider options shown in the screen and click finish. Now a trace rule gets added in the list of the feature.
5. Go ahead and hit the application in the browser and see the 500 error again.  Couple of files get created in the directory where you have configured the logs should go.
6. Open the xml file in Internet Explorer (MUST). If you open the xml in any other xml editor, you may not see the XML styles getting applied.

The opening page will show the errors and warnings that IIS has encountered while processing the HTTP request. Those traces will provide you a direction to troubleshoot the issue.

In particular to SharePoint 2010, the issue I faced was that the My Sites web application was not coming up and it was giving the 500 internal server error. When I did the Failed Request tracing explained above, I have seen couple of warnings in the log as shown below.

I opened the applicationHost.Config which is the one of the IIS metabase files where the details about Sharepoint14Module were present.

<add name="SharePoint14Module" image="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\isapi\owssvr.dll" preCondition="appPoolName=S………

The preCondition property value of this key is missing my application pool name in that list. I have added the application pool of the my sites web application and it started working.

Hope this helps for your troubleshooting and thanks for reading.

Manufactured Demand & Environment

Before reading any further, just watch each video. They do not take much of your time but give you lot of information. I am grateful to “The Story of Stuff” project for enlightening me and everyone.

I think the situation explained in these videos is not explicitly related to US but to all other countries. Consider the situation of bottled water. We all know, especially in India, how we use bottled water. How much environmental damage are we causing just for the water that we buy and drink? Although I had little idea about it, I realized its worse than what I have thought. And can you really explain why the plastic bottle waste is sent to India for recycling? Does the government of India realize that we are actually cleaning someone’s waste? Are we in such a bad situation to increase our revenue in all possible ways? Reasons like this are behind taking India for granted as a cheap country despite the fact that we are one of the fast growing countries in terms of science, technology and economy. Reasons like this are giving scope to the words like ‘Third World’. Why do we need to degrade ourselves like this just for money? I recollect the words by Amitabh Bachchan when he disliked Oscars being given to “The Slumdog Millionaire” where India is projected as a poor and backward country. Its not only the government, the politicians but also every Indian should consider this as a matter of self respect. No doubt that we need money but we do not need it the stake of self respect. Please do not fall for the manufactured demand. There are ways better than what we have now. As mentioned in the video, it is our right to ask Government to supply better water rather than relying on bottled water.
Just watch this video which is of completely different topic.

Can you guess what I am about to propose after watching this video? I am not going to tell you to stop using your toothpaste or soap or deodorant or shampoo. Because you would have already realized the facts around them. I am going to tell you the things that you already know of but, probably, never understood the importance of them. These are the alternatives to the cosmetics that we are using. Luckily these are part of our Indian tradition. The nature is giving a lot to us and there is no need to run behind these cosmetics. Neem or the Margosa sticks instead of a toothpaste is an alternative. Instead of soaps, you can use, Sunni pindi, a herbal bath powder. Use turmeric powder for healthy skin. How about using Reetha or Gooseberry (Amla) for head wash? Aren't they good an natural? We have to always remember that good and profitable things come in difficult way. Bad and harmful things come in an easy way. These cosmetic companies are experimenting on us? Isn't the Indian tradition more powerful than these products? Please come out of the manufactured demand. We do not need these. If someone asks me are you following these before telling someone? I would say no but I understood the importance of it and rather than using them now and then, I will follow them regularly from now.
The bad luck is that our (Indian) people are making fun of ourselves and our tradition. Let us not do that and let us not cause any more damage to our environment. We are already experiencing the results of the damage. Let us live and let others live by creating sustainable culture. Let us not throw waste just like that and let us not do things that cause damage to our respect. Thanks for understanding and following.
I am not going to talk about this video but just watch it, it is an informational one too.

A new threat, the micro beads. So updating my post.

           

“A web.config modification operation is already running” error in SharePoint 2010

It is pretty common that most of the enterprises do customize the SharePoint platform to a great extent by deploying solutions (WSPs) to the farm and associating features to those WSPs. When a feature is getting de-activated or activated, a web.config file change is triggered in the from of a timer job. This happens for almost all such operations. The file modification is done by an internally created timer job. It shows up as ‘job-webconfig-modification” when you execute the following command in SharePoint snap in loaded PowerShell console.

Get-SPTimerJob –Webapplication <ApplicationName>

There is another place where you can see the same timer job in “Run once” state. It is the Central Administration –> Monitoring –> Timer Jobs section. The job name should be visible as “Microsoft SharePoint Foundation web.config modification” job. This job should come up in the running job list for a while and then disappear as it gets removed after the modifications are done. As mentioned before, this is a run once job.

Getting into the problems, sometimes while activating or deactivating the features, you might receive this error (which is understandable from ULS logs) that a web.config modification is already running and this operation cannot be completed. This can be because you are trying to deactivate or activate features so quickly that you are not giving SharePoint the necessary time to complete its previous action. In some cases, although your previous action is complete a long time back, this still gives the same error. When I faced this error, I had no clue about what is happening because there is no feature activation deactivation that I did earlier nor I see the timer job in the PowerShell console. However I have learnt that the “Microsoft SharePoint Foundation web.config modification” job in Central Administration is present the job definition list and its schedule is stated as “Disabled”. I was not sure why it was not deleted after the feature deactivation/activation activity that I did before. It just remained there in the list disabled and it was stopping me from doing the current operation of activating features. I cannot take any action on that job except for leaving it like that DELETE it. I deleted the job and my current operation of feature activation and deactivation is now working :-).

So in case you are having similar issue and find such scrap job in your scheduled timer jobs list, please go ahead and delete it if it is in disabled state. This should work. I hope it helps and thanks for reading.

SharePoint 2010 ULS (Trace) Logs Not Working

This is one of the most common problems, I believe, with SharePoint 2010. You set up your brand new farm and configure the required logging levels in Central Admin – Configure Diagnostic logging page. However, you will notice that the log files get created in the folder you assigned the logs to be written to with no data inside them. The logs get rotated as usual but you will find the log file size as 0KB. The files are empty. Here is a solution for such problem scenarios.

There are absolutely 2 (or 3 more exactly) places where SharePoint administrators are exposed to tweak Logging mechanism of SharePoint out of the box. The Central Admin Monitoring Tab has a link to configure diagnostic logging settings which is the first place of interest for any administrator to change the logging settings. The other place is the “SharePoint 2010 Tracing” Windows Service which the actual engine that controls the logging on each individual server of the farm. This is the first point of check for the admins to see whether all the settings in Central Administration are configured properly and if this windows service is running. The same can be checked through power shell commands.

If you still see the same error, then there is a problem with security. In my experience, out of 5 farms that I have installed, these security settings were not properly implemented by SharePoint 2010 installation/configuration in one farm. I don’t know why. However, in order to fix it, please get the credentials with which the service SharePoint 2010 Tracing service is running. Make sure the user account is added to the local group “Performance Log Users”. It should be added to “Performance Monitor Users” local group as well. Restart the windows service after this change and that’s it. This should fix the security issues with the logs and logs should start rolling as per your configuration in central administration.

I read somewhere in the internet that even the application pool accounts should also be added to these security groups but I do not think so and I never had to do it to get the logs rolling.

Thanks for reading and hope this information helps in resolving any SP2010 logging issues you are facing.