Skip to main content

Busy All The Way - Part 3

Days 5,6,7 (Working Day 3,4,5) since I am free.

Never thought that jobless days would be as busy or even more busy than a regular day at office.
With the number of calls and emails being answered, it is quite a tough time to catch up with everything.

While overall the prospects are looking good, it is definitely a period of apprehension. The motivation to keep going is the good feedback that I am getting from my Interviews. I finally stopped all job hunt on Friday and decided not to continue with it until Monday.

Some things that I did to focus on the search are

1) Configure outlook so that my emailing has an office feel to it (and also to get rid of the Yahoo blue indentation while replying or forwarding emails
2) Configure Google calendar to sync with my Android mobile phone. Gets me organised with tasks and meetings. The plus point is that SMS alerts can be set for the meetings and I will get the location and reminder by SMS even if I have turned of mobile data to preserve power.
3) Update email signature, linkedin profile.
4) Add numbers to phone contact list as soon as I receive a call.
5) Tweak SOHO for job search

Had a technical interview on Day 7, more details later.

So long, friends.


Popular posts from this blog

SharePoint 2013 workflow : The server was unable to process the request

Here, I received another SharePoint 2013 workflow error. This time the workflow was not able to send emails and the following error was being shown Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP Unauthorized to http://sitename/_vti_bin/client.svc/web/lists/getbyid(guid'guid') Correlation Id: id Instance Id: id Fortunately I came across this post which gave me the answer Solution 1: In InetMgr, go to advanced settings for Security Token Service Application Pool and change "Load User Profile" to true. Recycle application pool. Reason 2 and Solution 2 : There could be another reason for this error. The workflow authentication can fail if the user executing the workflow (this will be the user initiating the workflow) is given permission through active directory group and the co

OWA not working after security update

Office web apps for SharePoint 2013 not working after security updates / server patching. After installation of the following security patches, OWA stopped working there by causing issues with SharePoint 2013. Details of ULS logs are provided below. FarmStateReplicator.exe (0x0CD8) Office Web Apps Farm State Error when trying to connect to Farm State Manager service: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http:// /farmstatemanager/FarmStateManager.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal