Showing posts with label migrated. Show all posts
Showing posts with label migrated. Show all posts

Wednesday, March 21, 2012

OLEDB TRANSACTION MAKING DIFFERENCE and error is raised

OLEDB transaction is making difference in my migrated application powerbuilder 10.5 which has new oledb driver which is replaced by MSS driver in previous Powerbuilder version.

1.)I am facing the below error on update/save this was not faced during my previous versino drive MSS in powerbuilder.This is oocure only after the change to oledb driver.

"Row change between retrieve and update.".

in front end of my application the error is poped as

"(STD1007) This row has been modified by another user. Save is canceled! ".

Please help to resolve this error.

Are you seeing this error when using Integration Services? If so, can you give more information on all the database access (e.g. ExecuteSQL, OLE DB Destination) in your package? If not, and this is specific to Powerbuilder, then I would start by looking at any settings available in your front end for handling database changes and transaction isolation level. If you want to focus on the provider itself, you can ask your question on the SQL Server Data Access forum, but they will likely have to rely on you to know how Powerbuilder is using the provider under the covers.

Tuesday, March 20, 2012

OLEDB error while processing Analysis service database

Hi,
I migrated AS 2000 database to AS 2005 thorugh migration wizard and started processing the database. But I am getting error like "OLE DB error: OLE DB or ODBC error: Query (5, 19) Parser: The syntax for 'AS' is incorrect..". After migrating I didn't modified any settings.
If anybody having info, please share.
ThanksIt looks the SQL query sent by Analysis Services for processing is bad. You can examine the query in the processing dialog and see what's wrong (wrong syntax for AS clause?).

Wednesday, March 7, 2012

Ole db error

Hi frnds,
New problems evryday ..
we had migrated our intranet website(in asp) frm win 2k t
win 2k3 last week , for 2 days all went ok but then the
trouble(s) started ...
frm yest we are getting an error time in and again
"Microsoft Ole DB provider for ODBC Drivers
error '80040e31'"
I have no clue as 2 why it is happening ...
the backend is sql server 2000...
plz help
Regards
JulainThat's the error number for Timeout expired. If using ADO,
try increasing the command timeout property. You can find an
example of this at:
http://www.able-consulting.com/ADO_Faq.htm#Q14
You may also want to consider using the OLE DB provider for
SQL Server instead of the generic OLE DB provider for ODBC
drivers. Generally you will get better performance, more
functionality.
-Sue
On Mon, 17 May 2004 21:58:40 -0700, "Julian"
<anonymous@.discussions.microsoft.com> wrote:

>Hi frnds,
>New problems evryday ..
>we had migrated our intranet website(in asp) frm win 2k t
>win 2k3 last week , for 2 days all went ok but then the
>trouble(s) started ...
>frm yest we are getting an error time in and again
>"Microsoft Ole DB provider for ODBC Drivers
>error '80040e31'"
>I have no clue as 2 why it is happening ...
>the backend is sql server 2000...
>plz help
> Regards
>Julain

Ole db error

Hi frnds,
New problems evryday ..
we had migrated our intranet website(in asp) frm win 2k t
win 2k3 last week , for 2 days all went ok but then the
trouble(s) started ...
frm yest we are getting an error time in and again
"Microsoft Ole DB provider for ODBC Drivers
error '80040e31'"
I have no clue as 2 why it is happening ...
the backend is sql server 2000...
plz help
Regards
Julain
That's the error number for Timeout expired. If using ADO,
try increasing the command timeout property. You can find an
example of this at:
http://www.able-consulting.com/ADO_Faq.htm#Q14
You may also want to consider using the OLE DB provider for
SQL Server instead of the generic OLE DB provider for ODBC
drivers. Generally you will get better performance, more
functionality.
-Sue
On Mon, 17 May 2004 21:58:40 -0700, "Julian"
<anonymous@.discussions.microsoft.com> wrote:

>Hi frnds,
>New problems evryday ..
>we had migrated our intranet website(in asp) frm win 2k t
>win 2k3 last week , for 2 days all went ok but then the
>trouble(s) started ...
>frm yest we are getting an error time in and again
>"Microsoft Ole DB provider for ODBC Drivers
>error '80040e31'"
>I have no clue as 2 why it is happening ...
>the backend is sql server 2000...
>plz help
> Regards
>Julain