UNSOLVED

thera

updated

14 years ago

T

thera

9 Posts

0

11716

December 14th, 2012 15:00

Android App "Unable to read from or write to the database"

I have tried several different android devices. All of them say the samet thing. I have also drilled down the log files and from the app and it says:

SEVERE: quest.android.appportal.connection.PNClient:  Broker Authentication error: Unable to read from or write to the database.. Code: 4313

Dec 14, 2012 6:40:59 AM org.apache.log4j.Logger error

SEVERE: quest.android.appportal.model.RdpThread:  Unable to read from or write to the database.

Doing this now I started logging the Broker on the server end and it says:

" 4313 Unable to read from and write to the database.

Any ideas before I contact support?

  • 1890

    0

    Posted December 17th, 2012 08:00

    Hi Thera,

    Do you have any devices other than Android tablets that you are using with vWorkspace, are they able to connect?

    If so, how are the Android devices connecting, is it over an internal network or via the Secure Gateway?

    You may also want to check that the application has not been orphaned;

    • open then vWorkspace Console
    • expand the Resources
    • select Managed Applications
    • right-click on your published application and select Properties
    • select the Publishing tab, ensure that the aplication is published to an RDSH server or desktop group
    • select OK to confirm any changes

    I hope this helps,

    David

  • thera

    9 Posts

    1890

    0

    Posted December 17th, 2012 13:00

    David,

               Appreciate your reply. Checked that before when I was going through the KB even recreated the desktop group from a scratch. Still the same. The web ascess part works fine from a regular desktop. Only the android app won't login. It goes all the way where it shows the name of the published application but clicking on it gives the error above.

    See if the pic below helps.

    Managed app.jpg

  • 1890

    0

    Posted December 17th, 2012 14:00

    Hi,

    How are the Android devices connecting, is it over an internal network or via the Secure Gateway? 

    Do you have other applications published, can the Android Connector launch those?

    Are there any special characters in the application name?

    David

  • thera

    9 Posts

    1890

    0

    Posted December 17th, 2012 17:00

    Nope, no other applications published, just that one. They are connecting straight to the server, no gateways nothing else. There are no special characters in the application name just as simple as you see it. HIIM VD or stuff like that.

    Thanks

  • 1890

    0

    Posted December 19th, 2012 07:00

    Hello,

    Grab yourself a broker log from the login attempt and check if the Broker gives the same message or not.

    If it is the same, raise a case with support.

    If it is different, feel free to still raise it with support or chuck the corresponding Broker log up here for us to look at.

    Thanks.

  • thera

    9 Posts

    1890

    0

    Posted December 19th, 2012 11:00

    Thanks Andrew,

                                 If you read the first post, you will see the second error line is from the Broker, I will still post the log file here if that helps. I have already opened a support call. I know whats wrong but I want to make sure the support is ok with the fix I apply before I do it.

                               As a matter of fact only the android app is affected, the Ipad app works fine. Desktop connector works fine too. Its just the andriod app crashing.

                               The database error 4313 points to corrupt database entries, can try to do a DBCC database check on it but I am going to ask support for further instructions. I will post the exact error from broker here soon. Appreciate it guys.

    Thanks

  • 1891

    0

    Posted December 19th, 2012 12:00

    Oops, missed that.

    I want to look at the broker log before and after that event. If you've sent it to support already, drop the SR number on here and I'll have a look through.

  • thera

    9 Posts

    1891

    0

    Posted December 19th, 2012 13:00

    Andrew,

    Attached the error log to SR 2034226, please search for this line in the Error Log

    19-Dec-2012 09:12:01 - 1436 : 2952

    You should see the 4313 error below that line. It has the screenshot of my android app giving the error too. The wierd thing is the application is listed properly so it is pulled up. Just cliciking on it blows it up.

  • thera

    9 Posts

    1891

    0

    Posted March 27th, 2013 20:00

    Allright this is for David and Andrew, who have been so helpful till now. To throw a new twisty,

    The andriod app works flawlessly on 4G/LTE/phone neworks. I tried multiple devices at multiple physical locations. It will just not work on wifi. None of the devices will connect to the VDI desktop on any wifi connection, be it at work/home etc. Nothing has changed since we last talked. The setup is still the same.

    I have opened a SR with the lowest priority. If needed I can post the SR # here. Let me know. Is there anyone on the forums who can check this for me too by trying to connect to a VDI desktop on vworkspace with an android connector exclusively over wifi and see if you get any errors?

    Thanks guys.

  • 647

    0

    Posted March 28th, 2013 09:00

    Hi,

    I found your contact details in the support system using SR 2034226, I havent found the new SR you mentioned tied to either your user account or site name. Can you let me know the new SR number and then upload a log to the support case so I can take a look.

    You said earlier that the connection is direct to the server with no gateway, is this still true?

    Are you able to launch a direct RDP connection to the server using the vWorkspace Android Connector?

    Thanks

    David