-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] mvGateway #48
Labels
Comments
jtillia,
Thanks for your input. We will look into this and see what we can do.
Thanks,
Dick Thiot
From: jtillia <[email protected]>
Reply-To: mvextensions/mvbasic <[email protected]>
Date: Wednesday, October 30, 2019 at 5:09 PM
To: mvextensions/mvbasic <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [mvextensions/mvbasic] [BUG] mvGateway (#48)
Describe the bug
we cannot save our work to D3 database item. It shows saved in the editor but is not on the server.
This works sometimes and other times not. It seems that once an item is not being saved, I cannot make it any time in the future.
To Reproduce
Change a line of code and Ctrl-S
Versions of applicable software
Detail on the versions of any and all pieces of software that are part of your environment, such as:
* Win 10
* D3 Windows/10.3
* MVBasic 2.0.1
Additional context
I don't know how to monitor errors, which must be coming from the Rest service through the gateway.
I deleted the remote system item and tried to save my code. Somehow I once was able to get
[image]<https://user-images.githubusercontent.com/56643358/67902570-dbc2d100-fb3f-11e9-8ef0-fff07aed337e.png>
But that was the only time I have had a message show up.
I have checked the "services on my laptop and started/restarted the MvGateway service." Since this works some of the time, so this does not seem to be a permissions on the service thing.
There are no messages in D3 errors file. There are no item-locks in D3 on these items.
we can see and list the files and items in the file. I can pull up the code to edit it.
I have not found any pattern to when it work and when it does not. Or what I am done. It happens 50% of the time I am saving items (ish).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#48?email_source=notifications&email_token=ACOODL4GWMG4AMLFOLYHCDDQRIA3BA5CNFSM4JHBAH6KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HVSPPPQ>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACOODL3FTZ6ID2DYEP4PEIDQRIA3BANCNFSM4JHBAH6A>.
|
We discussed this issue today. Sorry that we haven't addressed this in so long. I think that the problem is possibly related to the MVSP connection timing out. Could you try hitting F1 and Connect to MultiValue REST FS again? Have you looked at the Accuterm connector? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
we cannot save our work to D3 database item. It shows saved in the editor but is not on the server.
This works sometimes and other times not. It seems that once an item is not being saved, I cannot make it any time in the future.
To Reproduce
Change a line of code and Ctrl-S
Versions of applicable software
Detail on the versions of any and all pieces of software that are part of your environment, such as:
Additional context
I don't know how to monitor errors, which must be coming from the Rest service through the gateway.
I deleted the remote system item and tried to save my code. Somehow I once was able to get
But that was the only time I have had a message show up.
I have checked the "services on my laptop and started/restarted the MvGateway service." Since this works some of the time, so this does not seem to be a permissions on the service thing.
There are no messages in D3 errors file. There are no item-locks in D3 on these items.
we can see and list the files and items in the file. I can pull up the code to edit it.
I have not found any pattern to when it work and when it does not. Or what I am done. It happens 50% of the time I am saving items (ish).
The text was updated successfully, but these errors were encountered: