Tuesday, March 13, 2012

System.Runtime.Serialization.SerializationExceptio n:

Hello,
I'm getting the following error now with my aplication, but only when I run it ocally on my machine:
System.Runtime.Serialization.SerializationExceptio n: Cannot find member name System.Data.SqlClient.SqlError.
If I push the same build to a production server it runs without issue. This began happening suddenly and was working without issue locally on my machine. I've made no configuration changes to the machine except install windows updates.

Any ideas on how to get around this are much much appreciated..
ThanksHave you recently updated your local machine from .NET 1.0 to 1.1? Maybe you
are having this issue:
http://www.glacialcomponents.com/Ar...tionExceptio n

--
Hope this helps,
Bryant Hankins
Numinet Systems Inc.
http://www.numinet.com

"Really stuck" <Really stuck@.discussions.microsoft.com> wrote in message
news:1F535AEF-EA81-482B-B1AE-CFC7F7029B8F@.microsoft.com...
> Hello,
> I'm getting the following error now with my aplication, but only when I
run it ocally on my machine:
> System.Runtime.Serialization.SerializationExceptio n: Cannot find member
name System.Data.SqlClient.SqlError.
> If I push the same build to a production server it runs without issue.
This began happening suddenly and was working without issue locally on my
machine. I've made no configuration changes to the machine except install
windows updates.
> Any ideas on how to get around this are much much appreciated..
> Thanks
Thanks for the response Bryant.
unfortuantely no, the machine was running 1.1 all along as far as I recall.
REading that article, where can I make thoe changes? the web.comfig file?

Thanks again for your reply

"Bryant Hankins" wrote:

> Have you recently updated your local machine from .NET 1.0 to 1.1? Maybe you
> are having this issue:
> http://www.glacialcomponents.com/Ar...tionExceptio n
> --
> Hope this helps,
> Bryant Hankins
> Numinet Systems Inc.
> http://www.numinet.com
>
> "Really stuck" <Really stuck@.discussions.microsoft.com> wrote in message
> news:1F535AEF-EA81-482B-B1AE-CFC7F7029B8F@.microsoft.com...
> > Hello,
> > I'm getting the following error now with my aplication, but only when I
> run it ocally on my machine:
> > System.Runtime.Serialization.SerializationExceptio n: Cannot find member
> name System.Data.SqlClient.SqlError.
> > If I push the same build to a production server it runs without issue.
> This began happening suddenly and was working without issue locally on my
> machine. I've made no configuration changes to the machine except install
> windows updates.
> > Any ideas on how to get around this are much much appreciated..
> > Thanks
>
Yes. This would be a web.config or machine.config change.

--
Hope this helps,
Bryant Hankins
Numinet Systems Inc.
http://www.numinet.com

"REally Stuck" <REally Stuck@.discussions.microsoft.com> wrote in message
news:AB3A6781-E3DE-4ED7-A2E5-C78280FEA50B@.microsoft.com...
> Thanks for the response Bryant.
> unfortuantely no, the machine was running 1.1 all along as far as I
recall.
> REading that article, where can I make thoe changes? the web.comfig file?
> Thanks again for your reply
> "Bryant Hankins" wrote:
> > Have you recently updated your local machine from .NET 1.0 to 1.1? Maybe
you
> > are having this issue:
http://www.glacialcomponents.com/Ar...tionExceptio n
> > --
> > Hope this helps,
> > Bryant Hankins
> > Numinet Systems Inc.
> > http://www.numinet.com
> > "Really stuck" <Really stuck@.discussions.microsoft.com> wrote in message
> > news:1F535AEF-EA81-482B-B1AE-CFC7F7029B8F@.microsoft.com...
> > > Hello,
> > > I'm getting the following error now with my aplication, but only when
I
> > run it ocally on my machine:
> > > System.Runtime.Serialization.SerializationExceptio n: Cannot find
member
> > name System.Data.SqlClient.SqlError.
> > > If I push the same build to a production server it runs without issue.
> > This began happening suddenly and was working without issue locally on
my
> > machine. I've made no configuration changes to the machine except
install
> > windows updates.
> > > > Any ideas on how to get around this are much much appreciated..
> > > Thanks
>

0 comments:

Post a Comment