Zerbitzari bat izan zen, eta aspergarria gune bilduma backup komandoa exekutatzen Backup-SPSite PowerShell cmdlet naiz eta honako errorea lortu:

Backup-SPSite : Ezin Id edo URL objektu bat SPSite: ...  (mezu osoa azpitik)

Izan dut zerbitzari honekin arazorik egin du zerbitzari zela gaixo edo zerbait uste niri so.  Baino gehiago piztu dut ona zaharrak stsadm eta denbora honetan, hainbat errore bat jaso nuen:

Eragiketa hau, soilik ordenagailu bat hori zerbitzaria baserri batean elkartu egin daitezkeen ... (mezu osoa azpitik)

Jakina, it baserrian eta hori guztia, baina niri zuen dut hori gertatzen zen saioa nire kontu egin eta saioa normalean I sistema kontu bat zerbitzari honen gainean.  Hori egin nuen eta segurtasun kopia egin da.  Zer interesgarri aurkitu dut cmdlet eman zidan segurtasun-moztutako errore mezua.  Hori neat mota da, baina ez dit lagunduko askoz :) 

<amaieran />

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Izan dut nire dev txuletak berreskuratzeko lanean, eta horretarako, hobby bat proiektu hauek ditu bit lanean:

• Konektatutako web gune zati bat edo gune bilduma URL kutxa SharePoint Testua Filter web zati out bat jasotzen.
• This web part looks up all the info about the the selected site, generates an XML package and hands it off to another WP on the page (via connections).
• 3rd web part receives the XML and does some XSL transform stuff.

I wanted to rename the name space of all the bits to “Nivlag” and I was getting hit up with the following error when I deployed the web part to  my test environment:

This is a beginner’s problem but I thought I’d jot down a note on this anyway.  I caused the error when I right-clicked on the default name space (which defaulted to the project name), selected Refactor and then Rename like so:

That did rename things in a bunch of places in the project, but it’s not enough.  You also need to make several other adjustments:

1. Manually open up and edit a file, “ShaerPointProjectItem.spdata”. That an XML file that has a <SafeControls> section.  The namespace rename function isn’t aware of this file for whatever reason, so you need to update the Namespace there manually.

2. Manually edit the .webpart file.  For whatever reason, Visual Studio doesn’t change this reference either.  Change the "<mota>” node to reflect your changed namespace there.

3. Azkenik, depending on how you refactored the namespace change, visual studio may have also updated the string that references your .ascx file here:

You may need to change that back.  You’ll because you’ll get an error similar to the following when you try and add the web part to a web part zone on a  Orrialdearen:

Fix the reference there and you should be good to go.

4. Azkenik, the actual ASCX file still had a reference (for me) to the old original namespace (the refactor/rename function didn’t fix this).  You’ll know about this error when you try and add the web part to the page and get the following message:

Edit the .ascx file directly and fix the broken namespace.

Puntu honetan, I finally had a web part living in the namespace of my choosing.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin