Misleading authentication message from Studio #252
Comments
|
When you say "Control" and "Communicate". Do you mean start/stop server from the studio using run button and task manager? If so, I had a similar problem when I moved the 2.4.0 on High Sierra. I solved it by removing spaces in the path of Wakanda Server. Here is the path to my server as an example: Let me know if this helps. |
|
I tried that. See attached screenshots. It gives me the shown dialog box and cannot start Wakanda server in debug mode. To reproduce this I just have the Backend selected. I then click run on the server. I then get the dialogs after a lot of pinwheel spinning.
|
|
The two programs are inside my applicatons folder. /Applications/wakandaenterpriseserver.app |
|
Try only removing the spaces in the directory names, and keep the names of Wakanda Studio and Server as is. |
|
That's what I started with. My wakanda developer and server are in the root
of the Applications folder. When I renamed them I just had to sets the
prefs for wakanda.
…On Sat, Apr 28, 2018 at 8:12 PM Xiang Liu ***@***.***> wrote:
Try only removing the spaces in the directory names, and keep the names of
Wakanda Studio and Server as is.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#252 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA1AePZ-7yEv33hr4LE-IKnDzO7xu6sEks5ttQV6gaJpZM4TrlvP>
.
|
|
I checked the console as I tried to start the server and found the following Wakanda messages. error 21:12:23.531182 -0400 Wakanda Enterprise Studio nw_path_close_fd Failed to close guarded necp fd 31 [9: Bad file descriptor]
It times out for a while and then I get the administrator dialog box for Wakanda. |
|
This dialog box usually appeared when the solution as a user inside its Is this your use case ? |
JegoYann
changed the title
|
I was originally running from my standard user account and launching my solution from the Wakanda Enterprise Studio. I get this dialog box when I am trying to run with debugging on. If I run with debugging off. it works but makes development kind of hard. I did upgrade my standard user account to an admin account. but this did not help. I have tried using both my standard user username and password and my admin username and password. In both situations, I get the same results. It refuses to run and hangs up waiting for Wakanda server to start and respond. This started with Wakanda 2.4.0 and has stayed the same under 2.5.0. Prior to that, it was quicky about starting up especially in debug mode. I am running Wakanda Studio 2.5.0 on Apple High Sierra 10.13.4. |
|
Can you share your solution ? You can send me in private if necessary. Please provide also the couple user/password that is not working and the one that is working. |
|
That's the problem. I have no solution. It's not working. It can run a project without the debugger, but since I am using this machine to develop. It is nearly impossible to do so. But I can run the Wakanda Enterprise Server without the debugger. If I turn on the debugger it requires the passwords. Iy you would like to watch this in action contact me at naujocke@lcco.co.lucas.oh.us, call. You can then do a remote session and I can show you what it does. |
|
I mean, can you send me your |
|
Do you have a dropbox or place to put the zip file?
…-----------------------------------------------------------------------
MacCafe
7860 Central Ave.
Toledo, OH 43617
Phone: (419) 885-1240 X 241
Fax: (419) 517-2063
Eric Naujock - ACSA 10.2, 10.3, 10.4 Apple - ACTC 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, -ACSP 10.11, 10.12
http://www.mac-cafe.com
email: e <mailto:e@mac-cafe.com>ric@mac-cafe.com <mailto:e@mac-cafe.com>
AOL IM: erlic
On May 3, 2018, at 10:49 AM, Yann ***@***.***> wrote:
I mean, can you send me your Wakanda solution/project ? It would help to debug your issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#252 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA1AeG6ANYGTSEFS1nJO5tQVtBCQwmLDks5tuxjngaJpZM4TrlvP>.
|
|
I share a google drive folder with you. |
|
I have sent a zip of the full waked solution folder. I believe my git repository is in there too. And A copy of the 4D.4db database file. I am using 4D v16r6 to run the 4D. I cannot send the 4dd file. But the project depends on the 4d database. I only have the code in place for the public backend. But you will need the 4db file to recreate a blank database to wakened to talk to.
… On May 3, 2018, at 10:58 AM, Yann ***@***.***> wrote:
I share a google drive folder with you.
at ***@***.*** ***@***.***>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#252 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA1AeO7jCehw0eDmBzPDIrNV5-vb3WM2ks5tuxskgaJpZM4TrlvP>.
|
|
@erlicthemad Thanks. We are looking into it. By the way, just see in one of your screenshot that you have a weird Application name. |
|
I did rename the files back since it didn't help. But I was trying to follow the suggestion about filenames. I do not have my various versions of Wakanda on the machine. so my Wakanda programs are just at the root level of my application s folder. /Applications/wakanda-enterprise-server.app is the final path I put it back to. |
|
Reset it back and still get prompted for the administrator username and password. |
|
What is the mechanism that Wakanda uses to communicate from the Studio to the server? I am wondering if it's trying to use networking. I have a somewhat complex network setup. I have 9 network interfaces including VPN connections, USB, Thunderbolt, and usually 2 live network interfaces at any one time. Wi-Fi, and either my ElGato, or OWC interface. |
|
I have not heard anything back lately. I did do some other testing and created a new user account "WakandaTest" copied my project to it and tried to launch. I also tried to create a new project from scratch under the new user and neither one of these could connect to the server. It prompted me once for a password and then just hung claiming to be updating the server. 5 minutes later on a new project, it was still thinking about it. I also tried throwing out the development, and server program and reinstalling it from a new media. So far nothing is working to get the Wakanda development environment working. EIther under my normal working user account or the new WakandaTest user account. |
|
I did a bit more testing, and a new project on a new computer will work, and the debugger also seemed to work on a different computer with the same base operating system. So far from what I am finding is that there is something that is not user-specific in my main development workstation that is corrupt related to Wakanda. The problem also does not appear to be Project specific since a newly created blank test application will not work with Wakanda Server with either "No Debugger" or "Debugger" mode. |
|
This is frustrating. I just rebuilt my computer system completely from scratch. 14 hours later and Wakanda works as well as it did before. Will not run under diag mode. When watching the console I see that I am getting a security error exception 17.
appearantly there is an issue with wakanda and the com.apple.securityd. When I look it up it appears to be a keychain issue. Then when I try to launch the program I see the following error messages show up in my log.
At this point in time it still wont work or run locally. Now what to do? |
|
@erlicthemad Sorry for the delay. Just to be sure, which user account did you use ? You need to authenticate with the Wakanda user account. The one defined in the |
|
That worked. It wanted my Wakanda admin username and password. I lost two weeks worth of development time in Wakanda and 16 hours of pure downtime performing a complete rebuild of my system twice once on bare metal and once in a VM. Trying to troubleshoot the issues to find out that it wanted my Wakanda admin users password. This needs to be Fixed. It should make it clear then the prompt show up that it wants a Wakanda administrator account username and password. Right now I am dissapointed that a Silver 4D developer has to lose two weeks of production time due to poor documentation and lack of clarity in dialog messages. I posted a picture of the dialog box 16 days ago, and it took this much time to be told I needed to use my Wakanda Username and password. |
|
Thanks for your feedback. We will update the dialog message. This is the Community issue board. If your are a Silver 4D developer, using TAOW to communicate directly with the 4D support will ensure faster responses that respect your contract's SLA. |
JegoYann
changed the title
|
I used to do that, but I was instructed to use the Wakanda forums for things not related to 4d connecting to Wakanda. But yes we are a silver developer house using 4D working on using Wakanda to make web and IOS device access for the 4D database. On the 4d side, there is one person who tends to answer those questions. |
I have installed Wakanda 2.5.0 enterprise. I also had this issue under 2.4.0. I am currently running Mac OS X 10.13.4. I have been unable to get the Wakanda Enterprise studio to be able to control the Wakanda Enterprise server running on the same computer. I normally run as a standard user. I have tried to use both my local admin account username and password and my local username and password. It would seem that Studio is unable to communicate with the server. I have tried to promote my standard user account to admin and it does not help anything. It will start and run the application in no debugger mode. but that kind of makes it hard to troubleshoot the code. All communication is running through localhost. on the same computer. Is there a fix or a solution. This effectively makes Wakanda unusable for development on the backend. I still am able to use Visual Studio code to work on the front end code. It would be useful to be able to also tell Wakanda that is does not need to refresh the server when I work on front-end code in Studio.
When this happens it looks like the Server is running but is unable to communicate
The text was updated successfully, but these errors were encountered: