Error converting data type varchar to datetime.

Hi,

It is not exactly what I stated in the subject - It's an outcome - exception thrown while executing non-query command.

I get this exception when I try to execute my stored procedure that takes datetime as one of its parameters.

I am using dataset designer to create table adapters and build queries. Then I simply use objectdatasource component that uses one of the table adapters and bind it to for example a detailsview control.

When I run this in debug mode and trace the objects everything looks perfect including these datetime parameters. It is sql server that throws the exception. I ran the sql profiler to see what exactly is going on, and I captured the command that is sent by ADO - it's broken into several lines right in the middle of my datetime parameters... this is the source of the problem. Everything is working fine when I take this command and execute it as a single line in the sql management studio.

Is there anything about ADO that I do not know?

Is the error only with that particular SQL statement or anyother query with date? What datatype you are passing to the stored procedure? DateTime or varchar?

Thanks

|||

Are you passing date as string ? Are you sure that you date format is the same as default date format on SQL server?

If your date is not in valid format for SQL you can have this kind of problems.

Thanks

Error at deployment time (SSAS 2005)

Hello all,

May be somebody know what does this error mean:

"Error 1 Exception of type 'System.OutOfMemoryException' was thrown. 0 0"

I get it during deployment of cube after small changes I made in cube role.

When I deleted the role to return project to prviouse condition which was working, I still get the same error.

If anybody has any idea - it would be very appreciated.

Thanks

Inna

Hard to say on what is going on. Not clear which component produced an error.

Try connecting to Analysis Server from SQL Profiler and see if you will get the same error from the server.

Can you try and make changes to the role from SQL Managment studio and see if you are getting the same error?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

Hello Inna

Could it be possible that Your workstation has not enough memory for the Business Intelligence Studio ? You could also have some trouble in he Control Panel/System/Performance. I recommend a contact with Your System Support.

regards

Matti

|||

Hi Edward,

Thank you for your answer.

From SQL Profiler I didn't see my deployment process - when task failed it doesn't reach server and doesn't apply any changes there.

I tried and made changes to the role from SQL Management studio as you advised and it worked without any errors.

At the same time project stood not up to date and I don't know how to export the changes I made directly on the server to VS to continue development:

I can open Analysis Database in V Studio and make changes directly on the server.

After all I reopened the project, deleted role at all and got the same error.

Every time after reboot - it let me to make and to deploy changes for only one time.

Do you have any idea what could be a problem?

Thanks a lot

Inna

|||

Hello Matti,

Thank you for your reply.

Unfortunately now I have to work directly on the server (Windows Server 2003 Standard x64 edition - 6 GB memory and 1 CPU). BI studio installed there. When I get this error during deployment time – memory doesn’t grow out of 2 GB. So I thought enough is still available.

May be I need to configure BI Studio the way it can raise the memory it needs? - I have no idea if it makes sense.

I didn't notice any degradation in performance on the server at the time I got memory error.

All additional ideas would be much appreciated.

Regards

Inna

|||

Hi Inna again

You seem to have lots of memory.

I have met same error and same behaviour ones with my own Java application in Windows Xp.

In that case I could make the correction by changing in the registry the limit for the space of memory the operating system allocates to that type of applications.

Sorry, but I am not an expert in Windows Server 2003. I expect that there somewhere is a limit for the size of memory the operating system allocates to one task.

This is only a quess, but I hope it would be helpfull.

regards

Matti