Naoki Nakamichi Posted June 5 Share Posted June 5 I encountered an error when trying to use Spotfire Copilot from the Panel. The error details are as follows: Error occurred in ReadCore General error occurred. at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at SpotfireDs.CopilotCustomPanel.CopilotCustomPanelView.ReadCore(String method, String args, CopilotCustomPanel snapshotNode) The orchestrator and data loader on the backend are correctly set up. Additionally, the Spotfire user has administrative privileges. The settings in the Administration Manager are also completed, and the connection to the orchestrator URL from the Analyst is successful. Spotfire version: 14.0.2-HF09 Copilot version: 1.1.0 Link to comment Share on other sites More sharing options...
Marcelo Gallardo Posted June 5 Share Posted June 5 @Naoki Nakamichi Thank you for providing the details about the issue you're experiencing. Based on the information you shared, everything appears to be configured correctly. However, to further diagnose the issue, we need to review the Orchestrator container logs. We would appreciate it if you could share these logs with us. If you need any assistance with retrieving the logs, please let us know, and we’ll be happy to guide you through the process. Thank you for your cooperation and understanding. We look forward to resolving this issue promptly. Marcelo Gallardo Link to comment Share on other sites More sharing options...
Naoki Nakamichi Posted June 6 Author Share Posted June 6 @Marcelo Gallardo Thank you very much for your prompt response. Your support has been invaluable, and I appreciate your assistance in helping us move forward with resolving the issue. Unfortunately, when I reproduced the error from Analyst's Copilot, nothing appeared in the log. Also, there were no changes to the “server.log” of the Spotfire Server due to the Copilot's request. Accessing the swagger UI of Orchestrator from a browser in the same location as the PC on which Analyst is running, the logs were logged successfully. Logs were obtained with “docker compose -f docker-compose-orchestrator.yml logs”. orchestrator | INFO: 10.110.20.32:60768 - "POST /token HTTP/1.1" 200 OK orchestrator | INFO: 10.110.20.32:41874 - "GET / HTTP/1.1" 200 OK orchestrator | INFO: 10.110.7.170:43776 - "GET / HTTP/1.1" 200 OK orchestrator | INFO: 10.110.20.32:41880 - "GET / HTTP/1.1" 200 OK I have also attached the DEBUG logs from the Analyst. Please review them.(Some personal information, such as Google accounts, is masked.) Thank you once again for your cooperation and understanding. Best regards, Naoki Nakamichi Spotfire.Dxp.SupportDiagnostics.log Link to comment Share on other sites More sharing options...
Naoki Nakamichi Posted June 13 Author Share Posted June 13 @Marcelo Gallardo I wanted to apologize for the confusion caused by my earlier posts. After reviewing the issue, I realized that it was due to a configuration error on my part. Thank you all for your patience and assistance in helping me identify the problem. I appreciate your support and understanding. Best regards, 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now