none
QIK dll does not update correctly RRS feed

  • Question

  • Hello everyone

    Creating a dll using several powershell commands in QIK works perfect. But: Sometimes when I try to add an additional command to an existing dll, it doesn't work as expected. The dll is created without issues and I can build the OIP including everything it needs. But then when I register and deploy the OIP and I select the new activity for building a policy, the properties of the activity are not visible - the box is empty. Strange: When I use the QIK activity "Invoke .NET" and add the dll directly, the properties are there and work perfect!

    Any idea on this?

    regards
    Marcel


    SCSMfaq - http://blog.scsmfaq.ch ##### Microsoft Virtualization and Systems Management Partner http://www.itnetx.ch
    Sunday, April 3, 2011 6:39 PM

Answers

  • Marcel,

    This is something that happens with the current versoin of QIK (upgrading IPs is, to put it lightly, dicey).  We have given the Opalis product team feedback on this and they will hopefully be making some changes for the SCORCH release of Opalis (System Center Orchestrator).  For now I have gotten in the habit of creating a brand new IP every time (not doing 'upgrade').  Obviously this creates a lot of hassel updated all the old Policies that had objects from the previous version but it is the cleanest way for now.  As always, when developing IPs you should be importing and testing them in a 'development' Opalis environment not your production.  When we have a 'new' IP version I import it into our QA environment then update all the Policies that use it then during our maintenance windows for production remove the old IP, import the new (non upgrade) ip then export the policies from QA and import them into Prod.  Again, not that clean for now but hopefully the story will be better in the next version.

    -Ryan


    Saturday, April 9, 2011 10:35 PM

All replies

  • Hello Marcel,

    Did you hit Finish on the activity when you build the policy? If you hit Cancel or did not open the activity the data won't be available.

    Please check if this is a similar issue with yours.

    Not Properties and Published Data Visible
    http://social.technet.microsoft.com/Forums/en-US/opalisqik/thread/b2c39f1b-252a-40f3-aade-3c993798cc13

    Thanks,


    Yog Li -- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, April 7, 2011 9:17 AM
    Moderator
  • Hey

    I'm not sure what you mean with "did you hit finish". Of course I hit finish/OK and not cancel. Normally parameters are visible immediately after adding an activity. But not in this case. I have tested several things. Everytime I add commands to an existing dll, the parameters are not visible. One more thing: When I create a new policy that holds an activity that does not show the parameters, I am not able to check in the policy. I get an error that I should check the tracing logs. Means, it definitely seems to be a problem when building the OIP file from the dll because when using the dll directly (using the "invoke .net" activity) everything works perfect.

    Here are the 2 relevant Trace Logs that show some problems with the database (which is SQL server in my case). Any ideas?

    regards
    Marcel

     

    ***************************LOG 1***************************

    Process ID: 340
    Version   : 6.2.2.5229
    Computer  : MBR60
    User      : LAB\administrator

    2011-04-07 21:54:45 [2820] 1 COpalisManager::GetConfigurationValues::m_ipDataStore->GetConfigurationValues (HRESULT=0x80040E14)

    2011-04-07 21:54:46 [2820] 1 COpalisManager::GetConfigurationValues::m_ipDataStore->GetConfigurationValues (HRESULT=0x80040E14)

    2011-04-07 21:54:49 [2820] 1 COpalisManager::ModifyObject::m_ipDataStore->ModifyObject (HRESULT=0x80040E2F)

    2011-04-07 22:00:50 [2832] 1 COpalisManager::GetConfigurationValues::m_ipDataStore->GetConfigurationValues (HRESULT=0x80040E14)

    2011-04-07 22:00:53 [2832] 1 COpalisManager::GetConfigurationValues::m_ipDataStore->GetConfigurationValues (HRESULT=0x80040E14)

    ***************************LOG 2***************************

    Process ID: 340
    Version   : 6.2.2.5229
    Computer  : MBR60
    User      : LAB\administrator

    2011-04-07 21:54:45 [2820] 1 DBDataStore: ::GetConfigurationValues

    2011-04-07 21:54:45 [2820] 1 DBDataStore: ::Error #-2147217900
    Description: Conversion failed when converting from a character string to uniqueidentifier.
    Source: Microsoft OLE DB Provider for SQL Server


    2011-04-07 21:54:45 [2820] 1 DBDataStore: ::Exception caught in long __stdcall CODBDataStore::GetConfigurationValues(unsigned short *,struct tagVARIANT *):
    C:\AutomatedBuild\IS5.Platform\Branches\6.2_Sanitized\Platform\DBDataStore\ODBDataStore.cpp(11559)
    <Exception><Type>_com_error</Type><ErrorMessage>IDispatch error #3092</ErrorMessage><Description>Conversion failed when converting from a character string to uniqueidentifier.</Description><HResult>-2147217900</HResult></Exception>

    2011-04-07 21:54:45 [2820] 1 DBDataStore: ::Error #-2147217900
    Description: Conversion failed when converting from a character string to uniqueidentifier.
    Source: Microsoft OLE DB Provider for SQL Server


    2011-04-07 21:54:46 [2820] 1 DBDataStore: ::GetConfigurationValues

    2011-04-07 21:54:46 [2820] 1 DBDataStore: ::Error #-2147217900
    Description: Conversion failed when converting from a character string to uniqueidentifier.
    Source: Microsoft OLE DB Provider for SQL Server


    2011-04-07 21:54:46 [2820] 1 DBDataStore: ::Exception caught in long __stdcall CODBDataStore::GetConfigurationValues(unsigned short *,struct tagVARIANT *):
    C:\AutomatedBuild\IS5.Platform\Branches\6.2_Sanitized\Platform\DBDataStore\ODBDataStore.cpp(11559)
    <Exception><Type>_com_error</Type><ErrorMessage>IDispatch error #3092</ErrorMessage><Description>Conversion failed when converting from a character string to uniqueidentifier.</Description><HResult>-2147217900</HResult></Exception>

    2011-04-07 21:54:46 [2820] 1 DBDataStore: ::Error #-2147217900
    Description: Conversion failed when converting from a character string to uniqueidentifier.
    Source: Microsoft OLE DB Provider for SQL Server


    2011-04-07 21:54:48 [2820] 1 DBDataStore: ::(InternalSaveObject)

    2011-04-07 21:54:48 [2820] 1 DBDataStore: ::Error #-2147217873
    Description: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_OBJECTS_OBJECTTYPES". The conflict occurred in database "Opalis63", 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


    2011-04-07 21:54:48 [2820] 1 DBDataStore: ::Exception caught in long __thiscall CODBDataStore::InternalSaveObject(unsigned short *,unsigned short *,struct IXMLDOMNode *):
    C:\AutomatedBuild\IS5.Platform\Branches\6.2_Sanitized\Platform\DBDataStore\ODBDataStore.cpp(4284)
    <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 "Opalis63", table "dbo.OBJECTTYPES", column 'UniqueID'.</Description><HResult>-2147217873</HResult></Exception>

    2011-04-07 21:54:48 [2820] 1 DBDataStore: ::Error #-2147217873
    Description: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_OBJECTS_OBJECTTYPES". The conflict occurred in database "Opalis63", 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


    SCSMfaq - http://blog.scsmfaq.ch ##### Microsoft Virtualization and Systems Management Partner http://www.itnetx.ch
    Thursday, April 7, 2011 8:38 PM
  • Marcel,

    This is something that happens with the current versoin of QIK (upgrading IPs is, to put it lightly, dicey).  We have given the Opalis product team feedback on this and they will hopefully be making some changes for the SCORCH release of Opalis (System Center Orchestrator).  For now I have gotten in the habit of creating a brand new IP every time (not doing 'upgrade').  Obviously this creates a lot of hassel updated all the old Policies that had objects from the previous version but it is the cleanest way for now.  As always, when developing IPs you should be importing and testing them in a 'development' Opalis environment not your production.  When we have a 'new' IP version I import it into our QA environment then update all the Policies that use it then during our maintenance windows for production remove the old IP, import the new (non upgrade) ip then export the policies from QA and import them into Prod.  Again, not that clean for now but hopefully the story will be better in the next version.

    -Ryan


    Saturday, April 9, 2011 10:35 PM