Mas90 Providex Error
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full cannot open activation key file no valid activation found Time Job Ways to Get Help Expand Search Submit Close Search Login Join sage 100 1 user limit exceeded Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Providex Error sage 100 no valid servers found after reinstalling MAS90 Want to Advertise Here? Solved Providex Error after reinstalling MAS90 Posted on 2008-01-18 Tax / Financial Software 1 Verified Solution 3 Comments 2,534 Views Last Modified: 2013-12-11 After reinstalling MAS90 on several workstations, users are unable to launch MAS90. It gives the Providex error about not being able to find a valid license. I know this is a user rights error as I can launch the program on these workstations as local or domain admin and it runs fine. I am even able to log in as the user that is unable to actually launch the program once I launch it as Admin. A quick workaround I have found is to nest this users account with the local admin group. I don't want to do this for obvious reasons. I know MAS somehow creates a session key when you launch the program, but it is unable to do so for these users after the reinstall. The path to the share and the permission on the share have not changed, nor has the server information in the sota.ini (I can launch it as Admin). Any ideas? 0 Question by:cedarghost Facebook Twitter LinkedIn Google LVL 2 Best Solution byewlodarczyk In Version 4, Sage recommends that all users have local admin rights on the workstation. I understand that this is not possible in some environments. You could try checking the permissions on the local Go to Solution 3 Comments LVL 2 Overall: Level 2 Tax / Financial Software 2 Message Expert Comment by:ewlodarczyk2008-01-31 What version of MAS90 are you using? Is it MAS90 or MAS200? Also, can you please give me the exact text of the error message? Thanks, Ed 0 LVL 6 Overall: Level 6 Message Author Comment by:cedarghost2008-01-31 It is MAS200
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs https://www.experts-exchange.com/questions/23093706/Providex-Error-after-reinstalling-MAS90.html Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. MAS 90 (Sage) solutions Forum at Tek-Tips HomeForumsEnterprise ApplicationsERP and CRM Solution VendorsMAS 90 (Sage) http://www.tek-tips.com/viewthread.cfm?qid=830710 solutions Forum ProvideX:Initialization error on launch thread637-830710 Forum Search FAQs Links MVPs ProvideX:Initialization error on launch ProvideX:Initialization error on launch doliber (IS/IT--Management) (OP) 28 Apr 04 15:09 I have a customer that just upgraded to MAS90 3.71. Entire new network... Windows Server 2003 and new XP Pro workstations. All other workstations launch MAS error free and are functional. One machine however is throwing fits. I receive the above type error which states: Cannot open Activation key file - No Valid Activation Found!!I've worked with the support person on this and she believes it is a problem with the user account. I have deleted the user account from the server and recreated, added permissions individually for MAS to this user, disconnected the network drive; removed MAS, remapped the drive and reinstalled MAS. Same error when trying to launch. I then removed the computer from the domain, rebooted and readded. Same error when launching.Does anybody have any thoughts? RE: ProvideX:Initialization error on launch mrst
indicate operating system errors. In these cases, PxPlus returns the value of the operating system's error code (integer) plus 256. Use the MSG( http://manual.pvxplus.com/PXPLUS/appendix/list_of_messages.htm ) Function to obtain the error message that is associated with the number: ->?msg(4) Error #4: Device not ready This section provides a numerically arranged list of all the current error codes and their meanings. Error #0 Record/file busy Possible Reasons: • Cannot open a file that is locked by another user. • Cannot READ, FIND, EXTRACT, or INPUT no valid if a record is being extracted by another user. • Time-out occurred on a device. • Permission denied. The BSY=stmtref option allows you to trap Error #0: Record/file busy. Error #1 Logical END-OF-RECORD reachedCombined length of data elements cannot exceed preset maximum record length (as defined for your given file). Error #2 END-OF-FILE on read or File full on mas90 providex error write Possible Reasons: • On a read: The end of the file has been reached. or • On a write: The file is full or has reached a preset maximum record count. • [TCP] disconnection When PxPlus is processing a CLOSE directive and Error #2 is reported because of a full disk, the error is only reported once. Then PxPlus internally trashes the pending data and closes the channel. Error #3 Input/Output error on fileA physical (hardware) error was returned from a device. If errors are recurring on a disk drive, record and report them to your hardware maintenance supplier. Error #4 Device not readyA "not ready" status was returned from the device. If the device is a printer, see if it is out of paper or the off-line button has been pressed. Error #5 Data error on device or fileTypically reports a hardware malfunction: an error has occurred on a device during a read or write (most often on a read, indicating that the system is unable to read the data correctly). Error #