Idispatch error 3119

Hi, During an access to an Acess database I receive the following Error: [b]Com Error - IDispatch Error #3119[/b] Unfortunately it's a generic error dialog and

INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!

  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It’s Free!

*Tek-Tips’s functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Com Error — IDispatch Error #3119

Com Error — IDispatch Error #3119

(OP)

6 Aug 03 16:38

Hi,
During an access to an Acess database I receive the following Error:
Com Error — IDispatch Error #3119

Unfortunately it’s a generic error dialog and I can’t step through the code to find the actual place that generates it.

According to an error list on some obscure website the error #3119 is: Can’t group on MEMO or OLE Object <clause>. 

Since I didn’t code it I need a starting place to figure out which database table / query might be causing the problem.

Any suggestions?
(I’m cross-posting this in the VC++ Forum too.)

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Join Tek-Tips® Today!

Join your peers on the Internet’s largest technical computer professional community.
It’s easy to join and it’s free.

Here’s Why Members Love Tek-Tips Forums:

  • Tek-Tips ForumsTalk To Other Members
  • Notification Of Responses To Questions
  • Favorite Forums One Click Access
  • Keyword Search Of All Posts, And More…

Register now while it’s still free!

Already a member? Close this window and log in.

Join Us             Close

Running CORACLEANUP errors with: ErrorCode: -2147217873,WordErrorCode:3119, IDispatch error 3119, Violation of PRIMARY KEY constraint aud_ca_owned_resource_PK. Cannot insert duplicate key in object dbo.aud_ca_owned_resource

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers — Configuration Automation

CA Client Automation — Asset Management

CA Client Automation — IT Client Manager

CA Client Automation

CA Client Automation — Remote Control

CA Client Automation — Asset Intelligence

CA Client Automation — Desktop Migration Manager

CA Client Automation — Patch Manager

CA IT Asset Manager

CA Software Asset Manager (CA SAM)

ASSET PORTFOLIO MGMT- SERVER

CA Service Management — Asset Portfolio Management

CA Service Management — Service Desk Manager

Issue/Introduction

The following trigger on the ca_owned_resource table needs to be disabled.
Run the following sql command against the mdb to disable the trigger:
DISABLE TRIGGER dbo.ca_tr_upd_ca_owned_resource ON dbo.ca_owned_resource
After disabling the trigger, run CORACLEANUP again, then ENABLE the trigger again before running APM.

Environment

Release: UAPMAC990JPP-12.6-Asset Portfolio Management-Asset Configuration
Component:

Feedback

thumb_up
Yes

thumb_down
No

Hi Everyone,

i´ve got some trouble with the activity «query configmgr»:

Environment:

SCORCH 2012SP1 (upgraded DB from SCORCH 2012) and SCCM 2012SP1

If «query configmgr» is in any runbook,I´m not able to check in this runbook and get this error:

«An error occured saving the activity to the data storage. Please check the Orchestrator Management Service trace logs.»

So did I and found the following

2013-03-21 07:18:55 [2300] 1 CODBDataStore::ModifyObject({38C5285B-7812-4A14-B8C3-12E4260B31E2}): try again
2013-03-21 07:18:55 [2300] 1 DBDataStore: ::(InternalSaveObject)
2013-03-21 07:18:55 [2300] 1 DBDataStore: ::Error #-2147217873
Description: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_OBJECTS_OBJECTTYPES". The conflict occurred in database "Orchestrator", table "dbo.OBJECTTYPES", column 'UniqueID'.
Source: Microsoft OLE DB Provider for SQL Server
Error #-2147217873
Description: The statement has been terminated.
Source: Microsoft OLE DB Provider for SQL Server
2013-03-21 07:18:55 [2300] 1 DBDataStore: ::Exception caught in long __thiscall CODBDataStore::InternalSaveObject(wchar_t *,wchar_t *,struct IXMLDOMNode *):
ODBDataStore.cpp(3449)
<Exception><Type>_com_error</Type><ErrorMessage>IDispatch error #3119</ErrorMessage><Description>The INSERT statement conflicted with the FOREIGN KEY constraint "FK_OBJECTS_OBJECTTYPES". The conflict occurred in database "Orchestrator", table "dbo.OBJECTTYPES", column 'UniqueID'.</Description><HResult>-2147217873</HResult></Exception>
2013-03-21 07:18:55 [2300] 1 DBDataStore: ::Error #-2147217873
Description: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_OBJECTS_OBJECTTYPES". The conflict occurred in database "Orchestrator", table "dbo.OBJECTTYPES", column 'UniqueID'.
Source: Microsoft OLE DB Provider for SQL Server
Error #-2147217873
Description: The statement has been terminated.
Source: Microsoft OLE DB Provider for SQL Server
2013-03-21 07:18:55 [2300] 1 CODBDataStore::ModifyObject({38C5285B-7812-4A14-B8C3-12E4260B31E2}): attempt 10 failed

Now i searched for the UniqueID «38C5285B-7812-4A14-B8C3-12E4260B31E2» in the table «dbo.OBJECTTYPES» in the Orchestrator DB but there is no column with this id.

I uninstalled the Integration Pack for SCCMSP1 on the runbook designers and runbook server, restarted the server, registered the SCCMSP1-IP again but the runbooks still can´t be checked in.

As I saw, the DB-Entries for the SCCM IP were never deleted while the IP was not installed. 

Is there a way to force the IP-Installation to rewrite the DB-Entries? Maybe this way the Activity would get inserted to the DB?

Thanks for your help!

chri_tea 

  

Понравилась статья? Поделить с друзьями:
  • Identity v please retry error pc
  • Identity specification sql как изменить
  • Ibm error 2397
  • Ibm db2 error code
  • Ibexpert проверка базы данных на ошибки