Someone has any idea why the function MenuItemExecute("DIGSIG:CompareDocuments") wouldn't work when running on a WCF web service deployed in a server?
when I run it locally it runs just fine, does the job it is supposed to do. But when I deploy the app into a server, it gets 'stuck' in this call .
Anyone has any idea what could possibly be wrong?
In both machines, local and server I have Adobe XI Pro installed.
Thanks
For anyone that might be looking at the same issue, as stated before this cannot happen.
Acrobat cannot be used in a web service, but it can and will run on a Server unlike what someone from Acrobat staff said:
https://forums.adobe.com/message/8057317#8057317
Related
I have not found a solution posted how to download data from eikon/Refinitiv (I have my login/password) from my RStudio session that runs on a Unix server?
"eikonapir" seems to not work since it seems to required to run on an Windows OS.
Any help is appreciated.
What I have learned since posting this question is that:
RStudio running on a Unix system does not allow to connect to Refinitiv.
However, running locally (on my Windows Desktop) the Refinitiv application in the background using an advanced license and using a locally installed RStudio along with library(DatastreamDSWS2R) allows to connect to Refintiv's Datastream service.
While there could, of course, be an alternative solution and certainly a more technical explanation, I hope this does help.
Does anyone have any idea how this can be done?
It's my understanding that WebSphere 8.5 traditional is not compatible or will not run on OSX. I am looking for solutions for developers to develop with a WebSphere 8.5 traditional server locally.
Could we setup some servers on a windows machine so they can be used remotely during development?
I downloaded the Eclipse plugin but it gives me the warning saying OS X is not compatible with WebSphere traditional and to give it a remote server address. I tried to point eclipse to a server on a windows PC but it still wants a runtime installation directory.
I found a single thread on WASDev with a similar question talking about runtime stubs with a dead link.
I tried using a liberty server but I get nothing but null pointer exceptions and JMX errors, I don't think this is a valid alternative in my corporate environment.
For developing against WebSphere traditional on OSX, you could try Docker! We've published developer edition versions of 8.5.5.9 and 9.0.0.0, see:
https://developer.ibm.com/wasdev/blog/2016/06/15/websphere-traditional-ibm-http-server-docker-hub/
https://hub.docker.com/r/ibmcom/websphere-traditional/
The Dockerfiles used to produce these images are here, should you want to try building your own instead:
https://github.com/WASdev/ci.docker.websphere-traditional
However, your question is more specific to getting the tools working.
The last I read (and I'll try to confirm/update the answer when I do find it), is that the stubs are part of the full product install for RAD (selectable via Installation Manager).
You're correct that traditional WAS doesn't run on OSX. Remote servers are an option but traditional WAS is considered by some developers to be heavy and slow to restart, so your developers might appreciate something local and more nimble. Liberty is supposed to run on OSX, and things that run on Liberty -usually- will run on traditional, so getting to the bottom of your Liberty problems might be useful. If you haven't already, posting your question on WASDev might reach someone that has a better answer than this one.
I am building a client-server application, this is all running locally on my computer whilst I am developing the system. However, eventually I would like to deploy the server-side part of the application to a server to run 24/7, enabling client applications to connect and consume the service at will. What I would like to know is, when I come to doing this would I simply just install the server-side application on the server, hit run and that's it? That just seems... well not right (to me), is this the way it is done? or is there a lot more to it? I imagine there is, but I can't seem to find any content on this subject.
FYI - the server is a self hosted WCF application.
You'd want to take your program's executable, support dlls and config files and drop them into a folder. Then create a Windows Service to run the program; if you don't use a Windows Service, the program will only run while you're logged on, which isn't good. As a Windows Service, a reboot of the server will bring the program back online even if you're not logged on.
Here's a knowledge base article from MS on how to make a windows service.
http://support.microsoft.com/kb/251192
If you're program is compiled as a DLL, then create a small .exe program to run it (a wrapper) then deploy the program as described in the article.
Good luck.
Greetings,
we have to following problem.
Our application is deployed using ClickOnce. Everything is running fine and application is able to connect to the wcf service. The problem occurs when application is installed on FRESH XP machine without .net Framework and Windows Installater (that were selected in ClickOnce prerequities).
Application downloads .NET Framework 3.5SP1 and windows installer but then it cannot connect the the server. Reboot after install does not help.
The strange is that this application has been installed on 10 xp machines and 4 of them can connect to the service without a problem
Are there any dlls referenced in your application? You might want to check them (Under project's Properties\Publish tab\Application Files button) see if you missed to include the needed dlls or files.
alt text http://www.freeimagehosting.net/uploads/e8ff221e20.jpg
We ran into this and were forced to reinstall .net on some machines no idea why though.
This is a shot in the dark but have you tried depends.exe and see if it can profile what is happening.
Also Take a look at this blog and get a crash dump and see if you can use it to at least tell you what is complaining the loudest.
What do you mean when you say 'cannot connect to the server'?
a. The machine cannot connect to the install location and therefore the clickone app is not installed?
b. The app installs (along with the pre-requisites) and starts fine. Then it is unable to connect/communicate with your WCF services.
I presume (b) I just wanted to clarify.
What happens when you ping the machine the services are on from one of the failed install machines? Also what happens when you put the service url into a browser on one of the failed install machines? Can you see the wsdl?
Obviously your deployment package works because it works on those other machines (I assume it IS the same package all machines are installing?), therefore I doubt you are missing any dll's as a ClickOnce app should include all dll's it needs (sometimes you do need to tell ClickOnce explicitly to include).
Last question is, when the app tries to call the service, exactly what exception is it getting back?
I just remembered something which has caught me out in the past with some machines being unable to connect but others can...especially 'new' machines.
Check this file:- C:\WINDOWS\system32\drivers\etc\hosts
Check the contents on a machine that works and one that doesn't. We have some IP to machine name mapping going on that on new machines is not set and so the new machines cannot find the servers.
I am trying to get the svctraceviewer installed on windows server 2003. I found that it's part of the Windows SDK which is of huge size. Moreover, i wouldn't want install Windows SDK on a server unless it's a hot patch. Is there a way to download or copy the tool separately(probably from windows vista)?
Is there an alternative tool that can be downloaded with reasonable size?
Appreciate your response!
Your right, you probably don't want to push the Windows SDK to all of your servers! :) However, the SvcTraceViewer will run just fine by itself.
We copy it, and some other 'standard' tools to our servers to aid operators/developers in debugging those environments if absolutely necessary.
I don't know of any alternative tools that function as well as it does for specifically reviewing WCF/WF trace logs, but a protocol analyzer (NetMon, Wireshark) will let you see the network traffic. This doesn't help you if your problem is not at the wire level though!
Good Luck!