Ensure all profiles are marked, then Next.Hit Allow the Connection and Next again.In the Specific local ports field, enter the specific ports needed for your QuickBooks year version.Right-click Inbound Rules (later on, you'll create Outbound Rules), then pick New Rule.Enter "Windows Firewall" into the search and tick it.Open the Start menu on your Windows computer.To fix the error you're getting, let's configure your firewall ports and set up an exception to your anti-virus software. Hello there, appreciate you for trying some troubleshooting steps to resolve the script error page that pops up in your company file. Spicework user B-C made a comment related to the INI file which gave me this idea. I, however, feel chasing QB nearly everyday IS a complete waste of my time. This will ensure that each time the click the QB icon, the software starts in multi-user mode. point it at the quickbooks program folder and click a quickbooks program file.Ħ) Hide the original QB shortcut in the same place you hide the CMD file.ħ) Instruct the user to only use the desktop shortcut. Rename the shortcut so it reads legit, then change the icon. make corrections as needed)Ĭopy "%LOCALAPPDATA%\Intuit\QuickBooks 2018\" "%LOCALAPPDATA%\Intuit\QuickBooks 2018\QBWUSER.INI"Ĭd "C:\Program Files (x86)\Intuit\QuickBooks 2018"ĥ) Save the CMD file and create a shortcut on the desktop. It's in the same folder.Ģ) Edit the Multiusermode line to reflect "MULTIUSERMODE=Y"ģ) Make a CMD file somewhere that is not out in the users face.Ĥ) In the CMD file, make a copy command that copies your modified ini file over the orignial, then opens Quickbooks. After you relieve those machines (terminals) of the "hosting" package aka the DB Manager (there can be only one, the server!), you can do a simple little bait and switch of the desktop icon.ġ) Create a copy of the %LOCALAPPDATA%\Intuit\\QBWUSER.INI file. Seems when there is more than one, this pops up. Bookkeeping uses a few different company files and the problem always begins on those machines. We aren't but need to be able to do some logging to find why these errors ARE occurring and find resolutions to prevent them from occurring ongoing. This is a huge PIA administratively, and the admins are now being questioned as if it's something we are doing to cause this. It would appear that someone has scheduled an auto backup which would put the file into single user and then it's not being changed back to multi, but we can't seem to find who would be doing this.Īre there any settings to 1) disable users from making backups 2) disable users from switching to single user mode, 3) H202 seems to be fixed by a scheduled task where we restart the DB manager service, first thing in the morning. We've found that some users have been making backups and these backups are timestamped at times after the admins login in the morning, but before other users are logging in. The problem is that this is a nearly daily problem. Admins will again login to see if they can access, then find that they are now unable to access the file.Īll users have been dropped from the open files on the QB server, the admin will log in, set it back to Multi-User and then the users can get back in. Our admins have been checking the file in the morning to try and alleviate this and are finding no problems, but the users an hour or so later are getting this message. We're having a problem where users are coming in and logging on in the morning and then are being bounced with an error message (some -6190, -6073, H202) about single user mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |