The user is unable to use the copy/move wizard to migrate a "copy" of an existing SQL Server (Express) database to a host where SQL Server (Enterprise) is installed.
Example of the message:
SQL Server Scheduled Job 'QCDW_AHURASWDEV_AASPLE01_9' (0x7042C08C20C68441918F78DB22B4F0DC) - Status: Failed - Invoked on: 2008-09-26 09:05:11 - Message: The job failed. The Job was invoked by User sa. The last step to run was step 5 (Execute package QCDW_AHURASWDEV_AASPLE01_9_rollback).
The error states that the job could not access/locate files.
The user has changed the credentials associated with the Target SQL server services to ensure that the job has access to network shares.
The additional errors state how the job could not access/locate files.
Looking at the attached file (SharedFolderLocationField.doc), confirm if you have specified the correct shared folder. You may be specifying the wrong Shared Folder Location. The path being specified here should be shared on the SOURCE, which will be accessed by the TARGET.
E.g. You try to copy the database TestDB from server serverSrc to server serverTgt. Suppose database files are located in "C:\Program Files\Microsoft SQL Server\MSSQL$SS_2K\Data" folder of the server serverSrc. This location needs to be shared in order to serverTgt to see it. Let us say we created this share and named it "Data". In this case Shared Folder Location (see picture in attachment) should contain text "\serverSrc\Data", NOT "\\serverTgt\Data".
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center