Barnes and Noble Nook Review

[ad#singlepage]

I got my wife a Barnes and Noble Nook for Christmas… well I ordered it before Christmas. It shipped some time in January. In any case, I was really deciding between the Nook and the Amazon Kindle. Both of them were priced the same so it was a matter of the features that was going to determine the winner. They both have the same basic functionality such as E-Ink paper-like greyscale display, free wireless network access to download books, approximatly the same size screen and weight, and the ability to play mp3s. Some key features that I thought were an advantage over the Kindle:

  • Andrioid OS
  • Expandable memory slot (you have to remove the back cover to get to it)
  • PDF and EPUB format native support
  • 802.11b Wireless (only for use at B&N… for now)
  • replaceable battery
  • Small Color LCD screen (Menu and displays book covers…in color)

The Andriod OS has been making a splash on phones and many apps have been written for it. It is also fairly open which it was not a surprise when I found out that they hacked to nook to play Pandora over the free AT&T wireless network. Add the expandable memory slot with the 802.11b wireless capablitity and the possibilities are endless. Ok, maybe I’m overdoing it. The fact that you have a free AT&T wireless connection and an Android OS based device appeals to the hacker in me.

As far as reading ebooks, it does what is expected. You can adjust the font, font size and contrast so text is easier to see. Reading PDFs are as easy as connecting the nook to you PC via USB and copying the PDF to the mydocuments folder on the Nook’s internal memory storage. While you have your Nook connected, you can add some family photos to the mybackgrounds folder to see a grayscale version of your photo as a screen saver. You could also add some MP3 to listen to while you read, but at mono sound and with all the other mp3 players available, why bother. Since the Nook only uses battery to change the text on the screen and to power to tiny LCD screen, the battery life is  long as expected (days between charges). However, I noticed that if you have an extending reading session, like my wife sometimes does, you will have to charge it sooner than expected. One issue I had was the Nook would not charge when using the AC adapter, but it did charge using the USB directly to the PC. I called B&N support and after talking to an English speaking person, they shipped me a new AC adapter at no charge and with no hassle.

If you are considering an iPad versus a Nook for reading e-books, you are comparing apples to oranges. There is a distinct difference between an Apple iPad and the Kindle or Nook. That is the back-lit screen. There is a camp of people that can not spend an extended period of time reading text on a monitor or LCD. That’s why e-book readers have an advantage over a netbook or PDA. The e-ink technology is as close to reading paper as you can get and the battery life sweetens the deal. If you can spend hours reading on a monitor, don’t bother getting an e-book reader. Go out and get yourself a netbook or drop extra cash on the latest Apple gadget.

That said, the additional features on the Nook was the deciding factor in the battle of the e-readers. The only thing that I am worried about is how the Kindle market share will effect the number of ebooks available for Nook. Hope my decision pays off. Only time will tell.

[ad#singlepage]

Query notification processing failed due to a sql exception

We got this SCOM error last week along with a ton of the following warnings. Microsoft claims that this is a known issue that was supposed to be fixed with SCOM 2007 SP1 / SCOM 2007 R2, but I still encountered it running R2.

Event Type: Error
Event Source: DataAccessLayer
Event Category: None
Event ID: 26308
Date:  3/11/2010
Time:  11:30:01 AM
User:  N/A
Computer:
Description:
Query notification processing failed due to a sql exception.

System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 – The semaphore timeout period has expired.)
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.CheckThrowSNIException()
at System.Data.SqlClient.SqlCommand.InternalEndExecuteReader(IAsyncResult asyncResult, String endMethod)
at System.Data.SqlClient.SqlCommand.EndExecuteReader(IAsyncResult asyncResult)
at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryNotificationManager.HandleNotifications(Object state)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Health Service Modules
Event Category: Data Warehouse
Event ID: 31569
Date:  3/11/2010
Time:  11:30:03 AM
User:  N/A
Computer:
Description:
Report deployment process failed to request management pack list from Data Warehouse. The operation will be retried.Exception ‘InvalidConnectionException’: ExecuteScalar requires an open and available Connection. The connection’s current state is closed.

One or more workflows were affected by this.

Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
Instance name:
Instance ID: {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
Management group:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: HealthService
Event Category: None
Event ID: 2115
Date:  3/11/2010
Time:  11:30:39 AM
User:  N/A
Computer:
Description:
A Bind Data Source in Management Group has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectDiscoveryData
Instance    :
Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: HealthService
Event Category: None
Event ID: 2115
Date:  3/11/2010
Time:  11:30:39 AM
User:  N/A
Computer:
Description:
A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectAlerts
Instance    :
Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: HealthService
Event Category: None
Event ID: 2115
Date:  3/11/2010
Time:  11:30:39 AM
User:  N/A
Computer:
Description:
A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectPerformanceData
Instance    : yksc1s3.ehit.org
Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: HealthService
Event Category: None
Event ID: 2115
Date:  3/11/2010
Time:  11:31:18 AM
User:  N/A
Computer:
Description:
A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectEventData
Instance    :
Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: HealthService
Event Category: None
Event ID: 2115
Date:  3/11/2010
Time:  11:31:18 AM
User:  N/A
Computer:
Description:
A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectSignatureData
Instance    : yksc1s3.ehit.org
Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This is caused by a high number of sql queries to the Datawarehouse database. The work around is to add an override for the Event Data Collector rule in the Data warehouse connection server scope.
The Execution Attempt Timeout Interval Seconds property was changed from 0 to 6 and the Max Execution Attempt Count was set from 0 to 10. Restart the System Center service on the RMS and any gateway servers.

 

Copyright EverythingTech 2018
Tech Nerd theme designed by Siteturner