You are viewing limited content. For full access, please sign in.

Question

Question

Mobile - database not found, baffled

asked on April 9, 2020

When selecting to login to the Repository in the LF Mobile app I get a message "Database Not Found, Please Check the Name of the Database"

What database? I have no database on my phone? I see no configurations for entering any database.

Mobile doesn't use a database.

The mobile config and event logs are showing no errors.

0 0

Replies

replied on April 9, 2020

Hey Chad,

Laserfiche applications sometimes use the term "Database" as an internal reference to a repository. You might have noticed that WebLink and other LF web applications sometimes have a "dbid" parameter in their URLs that serves as a repository reference. I strongly suspect that's the case here, because as you correctly note Mobile doesn't use a SQL database.

In this case, you should check your repository configuration in the LF Mobile configuration page.

Cheers,

Sam

0 0
replied on April 9, 2020

Hi Samuel

First thing I did was double check the repository configuration, it is configured with no errors and no errors in the event viewer. Maybe there is a problem with the latest release of the app?

0 0
replied on April 9, 2020

 

  1. Was this a working configuration with an earlier version of Mobile Server that you upgraded and the issue is an emergent one post-upgrade?
  2. Is it a new installation of Mobile Server 10.4.2?
  3. Are there other Laserfiche web applications on the same server that can successfully connect to that repository? If they can't, sort out the networking issue first.
  4. Can you install the Windows Client on the same server as Mobile and verify that you can successfully login to the same repository using the same SSL/TLS connection setting? If you can't, sort out the networking issue first.
  5. Did you check the Windows Application and LFS event logs in addition to Mobile's? There's a chance a related error could surface in either of those.
0 0
replied on April 14, 2020

1. I could consider it a new install since we are trying out the lf app from the app store for the first time here, instead of using a web browser.

2. Yes, it is 10.4.2.207450 

3. There is Web Client and Forms and both work perfectly

4. Tried this and had no problem connecting to the repository, we do not use SSL

5. I did check the logs and there is no errors, but even on the configuration page there is no errors and I can remove and re-add the repository with no errors.

This is why I am not looking to the server for a problem, because I would see some kind of problem in the config page if anything was wrong. I just see that I can't login with the app on my phone when I choose to login to the repository.

Also I think by database it is reffering to something other than the repository, since all the configs refer to the repository as "repository name".

0 0
replied on April 14, 2020

Hi Chad,

This does seem strange.

1. When you access web client and it was successful, were you using a web browser from your computer/laptop? Was it from your internal network?

2. Is the mobile phone that you are testing with connected to the same network as in #1?

3. Can you access web client from your phone browser (not the app)?

Thanks,

Hui

0 0
replied on April 15, 2020

To access the web client I have been accessing it from my office outside. The mobile phone is using the same network as my workstation via WiFi. I have now tried from 2 networks, Comcast in San Jose and Cox in Vegas. I really don't see a networking issue here, what function fires the message for a failed database connection?

I just tried with a browser on my mobile and it works there as well. Web Access works fine, it is just the LF App that does not allow connecting to the repository only.

0 0
replied on April 15, 2020

Hi Chad, thanks for going through the testing. At this point, it would make the best sense to open a support case, so that we will have more data to dig further. 

Thanks

Hui

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.