![]() ![]() Sudo firewall-cmd -permanent -add-port=8019/tcp Sudo firewall-cmd -permanent -add-port=10172/tcp Sudo yum install samba gamin.i686 libgcc.i686 glibc.i686 libstdc++.i686 Once Fedora was installed I completed all the normal things you do on a new Linux install: disable root login via SSH, install fail2ban, set a static IP, gave my user account sudo access, etc So I had to track down version 27 from the archives: ![]() At first I tried installing the database manager on Fedora 30 and it did not like that at all. On a side-note I hope they will update the Linux database manager soon as the most recent version of Fedora it will run on is 27 and at the time of writing the current version of Fedora is 30. QuickBooks has a really great tutorial on their website on how to get the database manager installed but there were a few things that it didn’t mention so I thought I would make a post detailing the steps in case I ever have to do this again. That way we can rule out if the issues they were encountering are being caused by the Windows server. Everything was working great up until recently so as a test I decided to set up a Fedora server that would run the Linux version of the QuickBooks database manager and test hosting their company data files from it instead. I'm going to look in my share later to see what I come up with.I have a client that has QuickBooks database manager installed on a Windows server to allow multi-user access to the company data file. Get-Service -Name QBCFMonitorService | Where-Object | Start-Service (Be aware of what the service name is for your version of quickbooks database manager) Powershell.exe -file "C:\batch\Quickbooks.ps1 My solution is to create a powershell script connected to a batch file that runs every 15 minutes on the server to just start the service. I have called and spend hours and hours on quickbooks support with no resolution Then restart the Dns server service and then quickbooks database manager.įor a lovely explaination for versions 2017-2020 this link will show you how to reservesome ports to avoid the issue.Ģ: sometimes the db service will automatically just crap out and stop. If that can't be helped then the solution for older versions (older than 2017 version) is to goto Programdata > intuit folder and find a configuration *.TXT file and change the port listed. Solution: Don't install the DBmanager on a Domain controller. Some Enterprise antiviruses block the ports also.Īdditionallt the QB Admin should have the Message Service (I think its called that) allowing them to LOG Another user out of QBġ: older versions of quick books use the same ports as DNS. ![]() I also Make sure all versions are updated. These errors always happen when you install it on a DomaniController.Ġ: The first think I check is windows firewall ports, and go thru the chore of telling the client to make sure they go into and out of multiusermode correctly (Usually laminate a thin Sentence stating "Don't for get to switch to Multiuser Mode In QB!, and affixing it on their bezel. I have currently 12 clients with quickbooks, and this solution depends on what version of server your running and what version of quickbooks your running. The only issue they still have is resetting the DB manager constantly to allow multi user mode. As soon as we cut over the 2019 to be DC and GC with all roles, that issue disappeared. The only oddity that occurred, while we were running the both the SBS 2011 and the 2019 standard some users had issues getting to file shares, as in the connection just seemed very slow. Quickbooks support has no clue what's wrong. We have several servers with DB manager installed but this one is the only one giving us a problem. When they choose multi user mode it doesn't work until we click the scan button again. They can all get to the files just fine from the file share. Maybe for a day, maybe for a few hours, maybe for a week. We simply login, tell it to scan, accept the warning and it starts working. We can't find anything wrong, no errors reported by DB Manager, service is always running. Soon as we did almost every day they tell us they can't switch to Multi-user mode. We upgraded to server 2019 standard, installed QB DB Manager as we would normally. Customer had a SBS 2011 server running QB DB manager for their enterprise QB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |