Post reply

failed to create the share OMWWIZD

  • February 3, 2004 at 5:05 pm

    #76122

    I was trying to copy a DB with Copy wizard. The package failed with the error:"Failed to create the share OMWWIZD". The solutions in MS wesite did not apply to my case - both servers are running under the same domain account/password, with the same security settings. SQL2000 MSDE and Standart, sp3, win2003 storage server.

    There's no active connections to the DB.

    I did restore from the backup, but was wondering what it could be?

    Thanks a lot in advance.

    MJ

  • February 3, 2004 at 9:18 pm

    #492698

    I see Windows 2003  is in the mix.

    Here's my experience:

    I used the Database Copy Wizard to upgrade a Win NT, Sql 7 box to Win 2003, Sql 2000 and the upgrade failed for every database  -- with the same type of error message you're getting.  When I setup two Windows 2000 servers, ported the same databases over to one of the Win 2K servers, then did the upgrade to the other Win 2k server, the upgrade went smoothly. There's something about the enhanced security (i.e. disabed until enabled approach) of Win 2003 that confounds DTS. And I later found similar trouble with Win 2003, DTC, and Distributed Transactions.

    Bill

  • February 4, 2004 at 2:08 am

    #492717

    I would say insufficient permissions on the network.

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • February 4, 2004 at 10:13 am

    #492776

    Yes, I do not have a great network set up, but I still have to work around, right?

    I did try the same copy process from the second SQL server we have - the same config as the "BAD" one - win2K, sp4, SQl Standard2000, sp3, running under the same domain account. And IT WORKS! Why then the other server does not?

    What in the network could go wrong? Is there something I could check except the set up of the logins? But even the login is the same...

    Thanks a lot for all of your input.

    MJ

  • February 4, 2004 at 11:43 am

    #492779

    You may want to check This 

    YOU NEED LOCAL SYSADMIN PERMISSIONS ON THE REMOTE SQL BOX

    HTH


    * Noel

  • February 4, 2004 at 11:56 am

    #492780

    Please, read my initial posting - it said that both servers are running under the same PDC domain admin account, set up the same way on both SQl boxes - what more we could want? The only reason is that the destination box is SQL2000 MSDE, enterprise, sp3, win2003 storage server and the initial box is SQl 2000 standart, sp3 running on Win2000server sp4.

    It was also mentioned in the initial posting that I read the MS article...but it's not of any help for the same reason.

    That's why I was so confused. My confusion is even bigger today after I was able to copy from all of the other SQL servers in the company, but not from this only one!

    Thanks,

    MJ

  • February 4, 2004 at 7:49 pm

    #492825

    Unfortunately, I don't know the exact answer BUT as I said in my earlier posting, my experience matches yours. I believe that Win 2003 has certain RPC functionality disabled that is required by DTS.

    And I am a domain admin so it is not a simple case of permissions. In fact, after my first such failure, I tried exporting data from a sql 7  table to an empty sql 2k table using DTS.  It worked fine for a few but failed for others!

    I think this case is one for Microsoft to answer.

     

    Bill

     

  • February 5, 2004 at 12:27 am

    #492838

    I received this error message, because although I am sysadmin to SQL Server, I am nothing more than an ordinary user in terms of network privileges. Running the copy database wizard with domain admin right works fine. Don't know why, don't know how, but now I use detach-copy-attach procedures.

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • February 17, 2004 at 9:06 am

    #494384

    This might be the fix...

    I had the same error, the share might have already been created! Search both machines and delete it. For some reason it seems to be no error checking to see if this share is already there...and if it is it fails!

  • November 27, 2006 at 9:52 am

    #674105

    Yep,

    That was the problem in my experience.. it couldn't create the share cos the bloody thing already existed! (how bad a bit of programming is that?)

    Once I deleted the share (and had all the permissions and accounts organised) the database copied sweetly...

    Vida

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply