I have been using sesame server on a windows 7 box for over a year with absolutely no problems.

Today when users log in they can navigate around perfectly they can add notes but when they go to add a new record in the Main database Seasme goes south and gives a lost connection to server error.

Nothing has changed on the client or server machines or in the code.

If I take my files and move them to a machine using sesame server but not through the internet everything is fine.

What in the world could have changed? I have restarted server, gone to a backup of the database and still have same issue.

Below is the code on the button that I use to create a new order. when this is used we have the problem.

Thoughts?



// Save for safety
var vTemp as Int
var vNextNum as Int

If  @isblank(Status)
Then
{
     @Msgbox("This record has no Status", "Please Fix this record" , "Before Continuing")
}

Else
{

     If (@Mode() = 0) Or (@Mode() = 1)
     {
           GotoTabPage(LE0, 11)
           MGMDBY Holder = ""
           OeHide()
           forceredraw()      
     NotifyForm(-2)
     

           vTemp = @CreateNewRecord()
           PTIDGenerator()      
           DateRecordCreated = @Date
           RecordCreatedBy = @userId
           Status = "05"
           StatusAllupdatesub()

           @Color(LE17, 0,2) //command bar background
           @Color(LE38, 15,4) //recordof
           @Color(LE39, 15,4) //recordtotal
           ForceRedraw()
//writeln("should be 05")
           FormCommit("trak")
le38 = ("NEW")
Le39 = ("NEW")
           ThrowFocus(First)

           //adding()      
           ynUpdate()
           loadpres()


     }
}

Hi Robert,

Just to double check when you say BOBSCOTT wrote on Jul 5^th, 2012 at 4:56pm:


Sesame Server is on one computer and the Client is on another computer but still on the local network correct?

Your code isn't going to be causing this issue. What's happening is one of the ports we use to communicate Client/Server with is being closed, either on client side or server side. Since Client/Server works on your local LAN, I'd take a look at the firewall on the router and perhaps try turning it off and then back on as since this just started happening that should reset the router.

-Ray

BOBSCOTT wrote on Jul 5^th, 2012 at 8:18pm:



I don't see anything in the code that could cause a lost connection. That's why I was wondering if it was just a coincidence that it disconnects when you click the button but could also disconnect when you press F10 for example.

If you are sure it's the button, I mean you're the one testing it and looking at it not me, What I would recommend is commenting out say half of the lines, and try it. If it still does it, comment out half of the remaining lines. If it doesn't uncomment half your lines and test that. Keep doing this until you narrow it down. I would not be surprised if the last line standing would be a FormCommit(""), which does the same thing as an F10 and since it's a command to the server if the connection has been dropped, Sesame will tell you then.

-Ray