Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts

Wednesday, March 28, 2012

String was not recognized as a valid DateTime.

hi,

i just uploaded my web application to a remote server, everything works fine on my local machine..

but i m getting this error message on my remote server .. that is perhaps on the remote pc the sql server is handling datetime in a different format... how to check it and how can i set it up same as my local sql server date time format? or is there any other solution to it ?

String was not recognized as a valid DateTime.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.FormatException: String was not recognized as a valid DateTime.

in the database... column type is date time and and even this simple query is generating this error..

dim str as sqldatetime = sqldatetime.parse("Select 'datecolumn' from table")

thanks

Ok wich version of SQL server do u have on your pc and on your server?

That error might appear when you type a string in a wrong way

acepted formats in SQL SERVER EXPRESS 2005

01/01/2006

1/1/2006

1/1/06

1/01/06

1/01/2006

01/1/2006

01/1/06

I hope this helps


no, i m not inserting any date... when sumone gets registered to the system.. the stored procedure gets the date using function getdate() and i m just selecting it using .. a datareader and puting it in

sqlDateTime type variable... it is working perfectly in local pc.. that is sql server 2000 same is on the SERVER pcc... but i found one difference that in my pc it is storing date as mm/dd/yy and on server pc it is generating date using getdate() as yy/dd/mm... although did't change any settings....

and this format of yy/dd/mm is giving error when i retrieve it in variable sqlDateTime in asp.net!

even if i change its format in selection... then i wont work on my local pc.. because sql server on my local pc is generating date using getdate() as mm/dd/yy...

any help ?

thanks

Saturday, March 24, 2012

Strong Name Assembly

I have a strong named assembly. It installs fine on my XP Pro Machine via
the .net configuration tool. When I use the same tool to install it on a
W2003 machine it says it isn't strongly named.
As I don't have vs.net. Ihave been compliling my vb file as a module and
then using al.exe to sign it with a strong name. It seems to work on my
machine. When I copy the dll to the 2003 machine it doesn't. Does it need
any additional files than the dll. Also the W2003 machine is .net v2 whereas
my machine is .net v1. Any ideas? Regards, Chris.Get .NET 2.0 SDK (FREE) for you dev box and try it again

--
Daniel Fisher(lennybacon)
http://www.lennybacon.com

"Chris" <123@.123.com> wrote in message
news:uZ6CKud7FHA.444@.TK2MSFTNGP11.phx.gbl...
>I have a strong named assembly. It installs fine on my XP Pro Machine via
> the .net configuration tool. When I use the same tool to install it on a
> W2003 machine it says it isn't strongly named.
> As I don't have vs.net. Ihave been compliling my vb file as a module and
> then using al.exe to sign it with a strong name. It seems to work on my
> machine. When I copy the dll to the 2003 machine it doesn't. Does it need
> any additional files than the dll. Also the W2003 machine is .net v2
> whereas
> my machine is .net v1. Any ideas? Regards, Chris.

Strong Name Assembly

I have a strong named assembly. It installs fine on my XP Pro Machine via
the .net configuration tool. When I use the same tool to install it on a
W2003 machine it says it isn't strongly named.
As I don't have vs.net. Ihave been compliling my vb file as a module and
then using al.exe to sign it with a strong name. It seems to work on my
machine. When I copy the dll to the 2003 machine it doesn't. Does it need
any additional files than the dll. Also the W2003 machine is .net v2 whereas
my machine is .net v1. Any ideas? Regards, Chris.Get .NET 2.0 SDK (FREE) for you dev box and try it again
Daniel Fisher(lennybacon)
http://www.lennybacon.com
"Chris" <123@.123.com> wrote in message
news:uZ6CKud7FHA.444@.TK2MSFTNGP11.phx.gbl...
>I have a strong named assembly. It installs fine on my XP Pro Machine via
> the .net configuration tool. When I use the same tool to install it on a
> W2003 machine it says it isn't strongly named.
> As I don't have vs.net. Ihave been compliling my vb file as a module and
> then using al.exe to sign it with a strong name. It seems to work on my
> machine. When I copy the dll to the 2003 machine it doesn't. Does it need
> any additional files than the dll. Also the W2003 machine is .net v2
> whereas
> my machine is .net v1. Any ideas? Regards, Chris.
>