Do the service objects that your SMO is bound to already exist in the TEST environment? How were they created? They need to have the same GUID as their counterparts in DEV. I recommend creating a package from DEV that only contains the service objects and use that to get them created in TEST, that way you can be sure they are identical. Then create and deploy the full package of your application.

Hi,

Are you trying to map to a SharePoint 2013 service instance? If that’s the case, then the K2 for SharePoint must be registered on target environment.

Hi ,

Check whether the GUID's of the ServiceInstance's on both Development Server and TestServer are matching are not.

See the Screenshot

Hello,

Thank you for your tips.

Maybe I have to give you some more information.

The application was created on the DEV-System and afterwards deployed on the Prod-System.

The application is hostet in our SharePoint-Environment and all SMO's are created by the K2-integration tool for SharePoint.

The SharePoint-Sites and lists are registered.

@tbyrne777 The Package & Deployment from DEV to DEV works correctly and the system realizes that the objects are already there. But the Deployment from Prod to DEV doesn't work anyway.

@Vjay I can't see your picture.

Best Regards

Alex

Check attached now

I think the GUID is never the same in an Sharepoint Environment because the system will auto-create the list and library SMO's.

Have you tried matching those guid's in both environments and deploying the package, if no then give  a try and see what it says.

We have to edit the Service Instance, Not the Smartobject. See below steps ..

In Development Environment

1.  Open SmartObjects-Services-Tester Utility Tool.

2. Expand ServiceObjectExplorer. (See Attached Image)

3. Navigate to Sharepoint Service Objects Section. (It may be under Sharepoint 2013, Sharepoint Service V1/V2)

4. Identify and Select the Sharepoint ServiceInstance that was created for your sharepoint site and right click and select Edit Service Instance then click Next  to see the GUID. Copy it.

Now go to your Test/Production Environment and follow Step 1 to 4 and paste the GUID that's copied and save the service Instance.

Regards,

Vijay.

https://vijaydk2guy.wordpress.com

in prod environment, once you click edit service instance and next button, the old GUID appears... just remove it from the field and copy the guid from development environment