topic Re: Print is not working in WebAppBuilder in ArcGIS Web AppBuilder Questions

Print is not working in WebAppBuilder

mohannainar1 — Thu, 29 Mar 2018 12:51:10 GMT

1. It says "No Access-Control-Allow-Orgin" , my mapservice is not secured . I am using the web adaptor URL for print task .

2. ArcGIS Server and application both are running same machine.

3. I tried including this is code (esriConfig.request.corsEnabledServers.push("https://myserver");) in startup function of the widget , same error message I am getting.

Below is code am using for printing

_onBtnPrintClicked: function(){
var legendLayer = new LegendLayer();
legendLayer.layerId = "WidgetName";
legendLayer.subLayerIds = [0];
legendLayer.subLayerIds = [1];
var url = "https://servername/arcgis/rest/services/ExportWebMap5/GPServer/Export%20Web%20Map";
var printTask = new PrintTask(url);
var params = new PrintParameters();
var template = new PrintTemplate();
template.format = "PDF";
template.layout = "Layout";
template.layoutOptions = {//"legendLayers": [legendLayer], // empty array means no legend
"titleText": "Map Print",
"authorText": "xxxxxx",
"copyrightText": "yyyyy",
"scalebarUnit": "Kilometers",
"customTextElements": [{"titleID": "Map Reports"}, {"genderID": "All"}]
};
template.preserveScale = false;
debugger;
template.exportOptions = {
width:500,
height:600,
dpi:96
};
params.map = this.map;
params.template = template;
printTask.on("error",lang.hitch(this, this._printResultError));
printTask.execute(params, lang.hitch(this, this._printResult));
},

Re: Print is not working in WebAppBuilder

RobertScheitlin__GISP — Thu, 29 Mar 2018 13:02:13 GMT

Mohan,

If your map services and print service are using the web adaptor then there would not be the :3344 in the URL. You error like a url with :3344 in the url, so some url in your app is not using the web adaptor url and thus the app see that url as coming from a different machine.

Re: Print is not working in WebAppBuilder

mohannainar1 — Mon, 02 Apr 2018 05:19:49 GMT

I am running the application from web app builder that is the reason it is using 3344 , I will host the application in IIS and will let you know the output.

Re: Print is not working in WebAppBuilder

mohannainar1 — Tue, 03 Apr 2018 10:59:51 GMT

Now I have hosted the application in IIS, getting different error now. For smaller area( number of polygon geometry may be 5 or 10) the print works fine . For larger area (more number of polygon geometry) print is not working .

Proxy used in config.json file is

Getting an error like this

For smaller area the code works fine , for larger area the issue is there .

Re: Print is not working in WebAppBuilder

RobertScheitlin__GISP — Tue, 03 Apr 2018 12:58:10 GMT

Mohan,

I almost never use localhost. And you should not be using it in this situation

Re: Print is not working in WebAppBuilder

mohannainar1 — Wed, 04 Apr 2018 06:57:51 GMT

Same error I am getting, if i use server name also.

Re: Print is not working in WebAppBuilder

mohannainar1 — Wed, 04 Apr 2018 09:37:35 GMT

Robert,

So far I am using map service as BaseMap and I am able see the print output for smaller area . If I use the actual basemap (which I created ) , the print output is coming as blank.

Re: Print is not working in WebAppBuilder

RobertScheitlin__GISP — Wed, 04 Apr 2018 12:37:47 GMT

Mohan,

I am not sure why you are having such a hard time with this. So do you get any proxy errors in the console now?

You have your config.json set to always use proxy, that is not a good setting as everything does not need the extra step of going through the proxy (change to "alwaysUseProxy": false,). Is you app public yet, were I can test?

Re: Print is not working in WebAppBuilder

RebeccaStrauch__GISP — Thu, 05 Apr 2018 02:05:22 GMT

mohan nainar I'm having a similar issue with my basemap not showing up in my printout, but the rest of my layers do appear. Mine is not in WAB in this case, but is a JS web page. Just in case it is related or if there are common items, may be we can see a pattern Print GP service not printing cached basemap (AGS 10.5.1)

BTW rscheitlin , I did try the "alwaysUseProxy":false as you recommended, but no change, and the proxy is working for display of all tiled and dynamic the services. The print GP tool is not throwing any errors and seems to be working for all except the tiled basemap.

I have tested some addition things and will include them on my thread I link to above. In my case, I think this is a bug with the basemap tiled service in 10.5.1 ....maybe it doesn't like the v2 compact format of 10.5.1? The 10.2.2 basemap uses the v1 compact version.

Re: Print is not working in WebAppBuilder

mohannainar1 — Thu, 05 Apr 2018 09:02:44 GMT

I changed to alwaysUseProxy as false , even though I am getting empty base map in print. No proxy errors in console.Due to some restriction I can not publish the app in public.

Re: Print is not working in WebAppBuilder

RobertScheitlin__GISP — Fri, 06 Apr 2018 03:21:44 GMT

Mohan,

So do you have anything but the base map that is suppose to print in your web map?

Re: Print is not working in WebAppBuilder

mohannainar1 — Fri, 06 Apr 2018 07:11:42 GMT

Basemap and dynamically created layer (output of some process) . I want to print both but only dynamically created layer is appearing in print , base map coming as blank.

Re: Print is not working in WebAppBuilder

RobertScheitlin__GISP — Fri, 06 Apr 2018 14:14:37 GMT

Mohan,

What happens when you use the print widget and not your custom print code?

Re: Print is not working in WebAppBuilder

mohannainar1 — Fri, 06 Apr 2018 14:44:28 GMT

Robert,

My basemap is cached service, and its working from the print widget but not from custom print code. Whereas if I keep my basemap other than cached service (i.e. non-cached service), I can see the base map from custom print code.

Re: Print is not working in WebAppBuilder

RebeccaStrauch__GISP — Wed, 11 Apr 2018 00:45:56 GMT

esrimohan As mentioned above, I am having general issues with my cached basemaps not printing (10.5.1 in my case....my 10.2.2 serevice print just fine). I am working with tech support and have found a few things. Just in case these help you at all. FYI - we have several basemaps that we cache, and then turn off the layers in the mxd since the cache is what we want to use. So, check these things...

- Make sure all the layers in the mxd for your cache map service turned on (checked).

- Make sure all the datasources for your cached service still available

- if you have a mix of raster and vector data in the cached service, make sure they are all using the same spatial reference.

As mentioned, our 10.2.2 services work fine. Some of our cached services no longer have access to the source, which is ok since we just need the cache. We also have our services in the same SR as the raster layer, but had a few vector layers that projected on the fly. Again, it didn't matter in 10.2.2 since it would print from the cache.

Now it seems that the print itself is trying to be dynamic. I'm hoping they will have a workaround to force the print from the cache. I hope to know more in a few days.

This is all independent of the actual ArcGIS Print Service used (the out-of-the-box or custom, or the version), and independent of the API used. That is, we tested using the REST endpoint to take any API like JavaScript out of the equation. It also is independent of external vs internal-only, web-adaptor or not, etc. It appears to be the way the services and their caches are dealing with printing.

II'm not sure if this is relevant to your situation, but wanted to pass this along. Once I have a resolution, I will post on the thread link I mentioned above.

Re: Print is not working in WebAppBuilder

mohannainar1 — Thu, 12 Apr 2018 06:33:17 GMT

I cross verified the mxd file

1.All layers are turned on.

2. Datasources are valid

3.We have only one type of data(Vector)

We will wait for your response.

Re: Print is not working in WebAppBuilder

mohannainar1 — Tue, 19 Jun 2018 10:49:50 GMT

Hi Rebecca ,did you get any update ?