Showing posts with label record. Show all posts
Showing posts with label record. Show all posts

Thursday, March 29, 2012

Error Reporting in SSAS...

Is there a way to achieve the following on a UDM:

1) When an error occurs while processing a record
in a dimension, write the primary key of the record
along with the error to a record in a database.

2) Continue on all errors after logging them.

3) Launch a script when cube processing is complete
to notify affected parties of the errors.

Any suggestions to achieve something similar would
be greatly appreciated.

Filip

You can use SSIS package to put all that in one package.

You create a package using Analysis Services Processing Task. Then go to Menu -> SSIS -> Logging... In the Provider Type select SQL Server then check the "Details" tab. You have to try different Events and check it's logging all you want not more or less.

Continue logging on error is the properties setting on cube/dimension side also if you double click Analysis Services Processing Task you can set that in "Change Settings..."

Last one you have to query the log database table and use send email task in SSIS package.

Hope this will help - Ashok

|||

Thanks Ashok, I'll give that a try and report back ;-)

Filip

Tuesday, March 27, 2012

Error recording

Hi all,

I have an application in production that use a lot of stored procedures and the application doesnt record any error if any during the operation. (There is only a RESUME NEXT sentence).

So I want to know if there is a way to make SQL Server to register an error if any during the execution of a Stored Procedure without changing any of them. Say, that I want SQL Server to register an error during an execution of an user defined Stored Procedure as an internal error.

Thanks in advance.

God Bless.Is there a problem trapping the error in the application (get rid of the resume next and handle the error) ?|||Originally posted by rnealejr
Is there a problem trapping the error in the application (get rid of the resume next and handle the error) ?

Yes, the application is in the production environment and we have to solve the problem as soon as posible. If we change the code in the application then after that we should test the app, and we dont have time.|||Off the top of my head - you could use alerts (but that would be tedious) - do you know what errors you want to trap ?

Friday, March 23, 2012

Error on updating/adding record

I upsized (using Upsize Wizard) ACCESS back end to MSSQL 2000. Front end is still ACCESS. I'm getting error when trying to add or updated a record entry from front end.
The error message reads: 'Error # 3027 was generated by DAO.Recordset Cannot update. Database or object is read only.'

Thanks for any help.you should be using ADO not DAO

Wednesday, March 21, 2012

Error on inserting record on remote server

Hi,
I get this error when i insert a record from my local server to a
remote server.
Server: Msg 7391, Level 16, State 1, Procedure usp_insSO2NavAppV2, Line
14
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
pls help me
from
Doller
MSDTC might not be started on one of the servers
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"doller" <sufianarif@.gmail.com> wrote in message
news:1127785678.067089.75530@.o13g2000cwo.googlegro ups.com...
> Hi,
> I get this error when i insert a record from my local server to a
> remote server.
>
> Server: Msg 7391, Level 16, State 1, Procedure usp_insSO2NavAppV2, Line
> 14
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>
> pls help me
> from
> Doller
>

Error on inserting record on remote server

Hi,
I get this error when i insert a record from my local server to a
remote server.
Server: Msg 7391, Level 16, State 1, Procedure usp_insSO2NavAppV2, Line
14
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
pls help me
from
DollerMSDTC might not be started on one of the servers
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"doller" <sufianarif@.gmail.com> wrote in message
news:1127785678.067089.75530@.o13g2000cwo.googlegroups.com...
> Hi,
> I get this error when i insert a record from my local server to a
> remote server.
>
> Server: Msg 7391, Level 16, State 1, Procedure usp_insSO2NavAppV2, Line
> 14
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in th
e
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>
> pls help me
> from
> Doller
>

Sunday, March 11, 2012

Error number for duplicate column value during an insert for a unique column ?

I have a table in which a non-primary key column has a unique index on it.

If I am inserting a record into this table with a duplicate column value for the indexed column, then what will be the error number of the error in above scenario? OR How could I find this out?

Open a query analyzer and try to manually insert a value into the table and see what SQL complains..

|||

The error number for inserting duplicate value in a column of unique index is : 2601.

Wednesday, March 7, 2012

error messages

I got this particular error message..
18762 - Invalid begin LSN (%ls) for commit record (%ls). Check DBTABLE
as well as
Commit record at (%ls) has already been distributed. Check DBTABLE.
Also in the same server, I got this error
regardsm
bharath
Hi
According to http://support.microsoft.com/default...b;en-us;316783
this was fixed in service pack 2, therefore you may want to call Microsoft
PSS
http://support.microsoft.com/default.aspx.
John
"Bharath" wrote:

> I got this particular error message..
> 18762 - Invalid begin LSN (%ls) for commit record (%ls). Check DBTABLE
> as well as
> Commit record at (%ls) has already been distributed. Check DBTABLE.
> Also in the same server, I got this error
> regardsm
> bharath
>

error messages

I got this particular error message..
18762 - Invalid begin LSN (%ls) for commit record (%ls). Check DBTABLE
as well as
Commit record at (%ls) has already been distributed. Check DBTABLE.
Also in the same server, I got this error
regardsm
bharathHi
According to http://support.microsoft.com/defaul...kb;en-us;316783
this was fixed in service pack 2, therefore you may want to call Microsoft
PSS
http://support.microsoft.com/default.aspx.
John
"Bharath" wrote:

> I got this particular error message..
> 18762 - Invalid begin LSN (%ls) for commit record (%ls). Check DBTABLE
> as well as
> Commit record at (%ls) has already been distributed. Check DBTABLE.
> Also in the same server, I got this error
> regardsm
> bharath
>

error messages

I got this particular error message..
18762 - Invalid begin LSN (%ls) for commit record (%ls). Check DBTABLE
as well as
Commit record at (%ls) has already been distributed. Check DBTABLE.
Also in the same server, I got this error
regardsm
bharathHi
According to http://support.microsoft.com/default.aspx?scid=kb;en-us;316783
this was fixed in service pack 2, therefore you may want to call Microsoft
PSS
http://support.microsoft.com/default.aspx.
John
"Bharath" wrote:
> I got this particular error message..
> 18762 - Invalid begin LSN (%ls) for commit record (%ls). Check DBTABLE
> as well as
> Commit record at (%ls) has already been distributed. Check DBTABLE.
> Also in the same server, I got this error
> regardsm
> bharath
>