Skip to main content

Hi, 

 

I deployed and configured a full control K2 for Sharepoint App in my o365 enviornment. I am able to access it if I open my o365 site in a browser in the K2 Server but am not able to if I try to access K2 bits in another machine. Is it intended to work this way or am I missing a configuration step?

 

 

Hi Tejas,

 

Problems like this often refer to a DNS issue.

Make sure that the name you are using to access the server (in the URL) is registered in DNS.

It could be that this is not being picked up from other machines.

 

You can test this by pinging the DNS name.

If this does not resolve to the IP of the K2 server then this is your problem.

 

Please check DNS settings and try again.

 

Let us know if this works.

 

Kind Regards,

JohanL


If the previous suggestion didn't work  try is to make sure that the K2 sites are in your trusted sites in your browser. 

 

http://help.k2.com/kb001609

Configuration

  1. When configuring the K2 for SharePoint App in an on-premises installation and the K2 smartforms URL is added to the Configure K2 smartforms URL page the validating URL window will remain on the page with the spinner turning and no progress will be made.
    Workaround:
    a) Add the following to the Trusted sites zone:
    b) Add the K2 smartforms URL to the Configure K2 smartforms URL page and select Next.
  2. In certain environments, when opening the K2 Application page in Internet Explorer, the page remains blank. This is because the site of the identity provider (STS) and the SmartForms site are not in the trusted sites list and an infinite loop occurs.
    Workaround:
    In Internet Explorer under Internet options >Security> Trusted sites add the SmartForms site as well as the STS site.

also:

 

When using Internet Explorer as the browser an error stating "This content cannot be displayed in a frame" when working in a SharePoint online site.
Workaround:

Add the following URLs to the trusted sites list in Internet Explorer:
https://trust.k2.com
https://login.windows.net
https://login.microsoftonline.com


Hi Johan and Tim,

 

It was a DNS issue. Here are the steps I followed :

 

1. Mapped the public url to the https port (443) using a self signed ssl certificate issued to the public url.

2. Changed all the ssl data field values from https://<default-url> to https://<public-url>

 

and it worked :)

 

Thanks for all the help.


Reply