MYOB AE - Error 'Environment Error 1. Database has not been successfully converted'

	Summary
	The following information is only of relevance if you use Contacts or Viztopia with Compliance Integration to access AE Tax. The error message 'Environment Error 1. Database has not been successfully converted' may appear when opening Contacts. This error indicates the data files are in a prior version in relation to your program files.
	Detail
	When opening Contacts, Configuration, Viztopia Client Compliance or Viztopia Compliance Management, the following error message may be displayed: Environment Error 1 Database has not been successfully converted. Please contact your System Administrator and quote this number. Found version 42 [PDTSYS] Require version 43. The error indicates the data files are in an earlier version to your program files. This indicates that the database has not been upgraded to the latest installed release or service pack version, OR You are using a desktop shortcut that is pointing to an old program location. To resolve this issue you need to: First check if any shortcuts to Contacts or Configuration on your Desktop open old, invalid, copies of the MYOB AE software. If they do, the please delete these shortcuts. If this is not the case, then you will need to re-convert the database and reinstall the upgrade (for cases where this procedure has not completed successfully). Steps: 1.      Locate the Program Directory; 2.      Re-convert the Databases; 3.      Reinstall the Integrated Release (if it was interrupted by the error 'Environment Error 1'). How to locate the bin folder, ie the Profiles program directory Note: The following instructions do not apply to Terminal Server sites. For Terminal Server users, the required ceedata.ini file is located in the path: C:\Documents and Settings\{username}\WINDOWS 1.      At the Windows Desktop, click Start and select Run. The Run window appears. 2.      Type ceedata.ini in the Open field and click OK. The ceedata.ini window appears. 3.      Note the PROGRAM_DIR directory (e.g. S:\MYOB\bin) and the CHOME directory (e.g. S:\Data\). Note: Please make sure that you DO NOT have a UNC path for either the PROGRAM_DIR or CHOME directories, eg \\servername\sharename in the ceedata.ini file. If a UNC path is present for either directory, this MUST be replaced by the absolute path, eg S:\MYOB\bin and then your changes must be saved via the menu path File > Save. 4.      From the File menu, select Exit. How to re-convert the database 1.      Open Windows Explorer, and browse to the Profiles program directory identified above, eg S:\MYOB\bin. 2.      Double-click on the file DatabaseSetup.exe to start the Database Upgrade. Select the required database(s) (start with the database stated in CHOME path), and step through the upgrade wizard. It is recommended that you select to convert just one database at a time at this stage. 3.      If the Database conversion wizard does not open, then there may be a licensing issue which can be corrected by running the Register.bat file. This file is also located in the Profiles bin folder. You should be able to step through this wizard by accepting the current details. The Select Components window is displayed. 5.      Click Next. The Register Solution 6 Software window appears. 6.      Enter the Registration Code provided by MYOB and click Finish. The message "Your registration code has been accepted" appears. 7.      Click OK. The system may take a few minutes to process. Note: If you get any errors during steps 2 to 5, please submit a support request quoting article number 13652 with the details of the error. How to run the Application Finder Note: If during the conversion of the database, a message states that the database is locked, please follow the instructions below to find the user that has it open, otherwise skip this section. 1.      From DataSafe, click Support Tools. The MYOB Database Utilities window appears. 2.      Select Application Finder from the Utility drop-down list and then click Run Now. The Application Finder window appears. 3.      Note the programs running and shut down all applications, except for DataSafe which is denoted by the 'backup.exe' record in the Application column. 4.      Click Refresh. Only DataSafe which is denoted by the 'backup.exe' record in the Application column should be displayed. 5.      Click Close. The DataSafe Utilities window appears. 6.      Click OK. The Windows Desktop appears. To confirm that the database has been upgraded correctly, please open Contacts (it will open if the installation failed). Close it again and reinstall the Integrated Release if the installation has not been completed successfully.

MYOB AE - "Error: The user profile could not be written. "

If you continue with the existing workpath, the error 'Cannot login without a valid workpath.' occurs and you are then returned to the System Services login gate. Changing the workpath in the field provided, returns the error, 'This location is read only'. The errors will then continue preventing access to System Release for that user.

This error is due to an existing corruption in the ds6op050 file. This file contains information relating to users':

·         Customized toolbars;

·         Navigation favourites; and

·         Window sizes.

To correct this issue the ds6op050 will need to be renamed.

Renaming the ds6op050 file

1.      Double-click the My Computer icon and navigate to the drive on which your Sol64 folder is located.
The contents of the drive appears.

2.      Double-click the Sol64 folder.
The contents of the Sol64 folder appear.

3.      Right-click the ds6op050 file and select Rename.
The file name changes to edit mode.

4.      Rename the file to ds6op050.old and press ENTER.
The change to the file name is saved.

Open System Release in the usual method and access is now possible.

Customised toolbars and navigation favourites will then need to be manually recreated.

Configure Access to Entire Exchange 2007 Mailbox Database

Source URL:
http://technet.microsoft.com/en-us/library/bb310792%28EXCHG.80%29.aspx

* In the Exchange Management Shell, use the following command to
allow access to all mailboxes on a given mailbox store:
Add-ADPermission -identity "mailbox database" -user
"serviceaccount" -ExtendedRights Receive-As

* In the Exchange Management Shell, use the following command to
allow access to an individual mailbox:
Add-MailboxPermission -identity "user" -user "serviceaccount"
-AccessRights FullAccess

To do the same for Public Folders:

*To add AllExtendedRights permissions for the user Chris to access
the public folder named Marketing, run the following command:
Add-PublicFolderAdministrativePermission -Identity "\Marketing"
-User "Chris" -AccessRights AllExtendedRights -Inheritance SelfAndChildren