Monish Nagisetty's Space

Building connectivity on-premise, in the cloud and beyond

Best Buy and Your Personal Information

I was at Best Buy today and I decided to sign up for the Reward Zone Program. The rep at the register asked for my phone number and instantly pulled up my personal info.  A quick glance at the screen indicated that they had my home address and phone number. They probably captured this info when I first swiped my credit card without any fear.  In fact,  now I am sure that they also capture my purchases and returns to track my buying behavior.

Just then it hit me! If best buy collects my personal information, how many other retails stores do the same? I already know that online stores collect and probably store my information.  But my main concern is not that the retailers store my personal info but whether they store it in a secure manner. Sure the big retailers may have security procedures to handle sensitive information. But what about the small ones? How many of them can you trust? How many of their systems are being breached right now? Who knows…But recent incidents at DSW and Lexis Nexis tells me that it is certainly possible. The information overload is sure to seap through the cracks somewhere.  Someone may already be cracking these retail systems to get at your personal info.  If my assumptions are correct, then the number of sources to get at your personal info are already plentiful.  Let’s hope that some of them are not poorly secured.


December 29, 2005 Posted by | Observations | | Leave a comment

WSE032: There was an error loading the microsoft.web.services2 configuration section.

I haven’t posted anything in a while so here goes.  I recently ran into a WSE032 error when I ran my web service client application.  It just would not get past the point where the web service proxy was being initialized.  Also, the stacktrace did not provide any details as to where the error actually occured.  See the stacktrace below.  It turns out the problem was with loading some of the web service filters I had added to the section of the configuration section.  The filter references were not using the fully qualified strong name assembly naming conventions.

I had
instead of
        SampleFilter, WSELib, Version=, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxx” />

As soon as I modified the type attribute to use the fully qualified assembly strong name I no longer ran into the exception. 

WSE032: There was an error loading the microsoft.web.services2 configuration section.
   at Microsoft.Web.Services2.Configuration.WebServicesConfiguration.Initialize()
   at Microsoft.Web.Services2.Configuration.WebServicesConfiguration.get_ReferralConfiguration()
   at Microsoft.Web.Services2.Referral.ReferralCache.Initialize()
   at Microsoft.Web.Services2.Referral.ReferralCache.ResolvePath(Uri uri)
   at Microsoft.Web.Services2.WebServicesClientProtocol.set_Destination(EndpointReference value)
   at Microsoft.Web.Services2.WebServicesClientProtocol.set_Url(String value)
   at XYZCompany.AppName.Client.WsClient.WsClientWse..ctor() in reference.cs
   at XYZCompany.AppName.Client.WsClient.Main() in WsClient.cs

December 28, 2005 Posted by | Web Services | | Leave a comment