Cannot access the repository from SPSS Modeler client v16.0
Previously I am able to access the C&DS repository from Modeler Client application in the notebook installed in Windows 7 version. Recently the notebook OS was updated to Windows10, we had reinstalled the Modeler client v16.0. We realized that we are unable to access the repository which was working previously. I did not find any relevant error that log the issue from modeler server and client. I had checked there is no firewall and port issue. Kindly advice.
Hello @shirleen,
Thank you for your post. Please note that Modeler 16.0 is not supported on the Windows 10 platform. While we will strive to do our best to resolve your issue, if we cannot replicate this issue on a supported platform, our abilities to engage additional resources may be limited. For reference, supported Operating Systems for Modeler 16.0 can be found here.
With regards to your issue at hand, which version of C&DS are you attempting to access with SPSS Modeler Client? Additionally, do you have the C&DS Deployment Manager Client application installed on the same host as Modeler Client and see if the same issue occurs?
Finally, can you attach a screen capture of the error you are observing within Modeler Client when you attempt to access the repository?
Kind regards,
As I have 2 environment, testing & production environment, It occurred that only the testing environment is having the issue. Both environment installed C&DS v6.0. Hence I am not convinced that why is it that the modeler client (same notebook) could not access the testing environment. We did not install C&DS Deployment Manager Client application on the notebook to try.
Kindly advice.
[1]: /answers/storage/temp/14464-spss-unable-to-connect.jpg
Thanks for your reply. The screen capture you have shown has two main causes: 1) The WebSphere profile housing the C&DS application is not running; or 2) Your client firewall is restricting access to the C&DS host;
You mentioned in your initial post that you've checked the firewall/port is not an issue, how did you verify this?
Can you install the Deployment Manager client on this Win10 machine to make sure the problem is not with the Modeler 16 application?
Hope this helps,