Thank you for efforts and your willingness to make this available,

Dan

Great tool! I didn’t think it was possible to go and look into the database to pull files, but wow! Then again, I’m not exactly an advanced MOSS administrator, either!

I did have two questions though:
#1: After we export the docs.xml (metadata) and attachment_docs.xml (linked file), HOW do we get it into our new server? I know it exports it, but if everything is listed in an XML file, I’m unsure of how to get the files into a document library and show metadata. Do you have a how-to on how to do this, or a quick rundown on what to do?

#2: I keep getting the following error after it says “Export has been interrupted because of an error!”:
“System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)”, etc etc. It was a fairly long message that it gave, but I was unable to copy/paste, so I just typed that above :p

Any ideas?

SQL Servername:
“\\.\pipe\mssql$microsoft##ssee\sql\query”

Looking forward to utilizing your app, many thanks for publishing it.

Pascal.

Database Server:
-’SERVERNAME\Microsoft##SSEE’

SQL Server Database Name:
-’WSS_Content’

I have tried a combination of just ‘SERVERNAME’ with and without the ‘\Microsoft##SSEE’. I’ve also tried ‘WSS_Content’, ‘SQLExpress’, ect for the database name. I’ve tried all of the above with both authentication types with a known account with full admin rights. I’ve tried running this app on the server itself and remotely on my management workstation.

I would really love to be able to utilize your tool, it would be the perfect fit for our environment. Are there any suggestions you may have where I may be going wrong?

Thanks for your time,

Joe

For version compatibility… Latest version I tested was Sharepoint 2007. I have heard that it is working on Sharepoint 2010 but I never tested it.

Pascal.

I have pulled both the database server name and the database name from the Central Administration tool, however I receive the following error:

System.ApplicationException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (providers: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)
at Sharepoint.DBExporter.ExecutionContext.Create(ConnectionDetails connectionDetails)
at Sharepoint.DBExporter.Program.GetContextFromUser()

Any help would be greatly appreciated,

Thanks for your time,

Joe

I ran a SQL script to update the DocVersions table and this allowed the document versions to be restored with the metadata. Before running this script, I grabbed the Siteid and Id of the document which was going to be restored from the destination database’s docs table

Hope this helps others as well.
Ushi

When I first developped the exporter, I had the idea of building another software that is able to import external data into a live Sharepoint environment using the Sharepoint API. I never had the time to do it…

About your first point, that’s a good idea to be able to export all revisions of a file at one time. I will take a look to see if I can do it.

Pascal.

Another think I would really like is to be able to grab the document, all its versions with the metadata from the backed up database and be able to restore it to a sharepoint document library in the current working database.

Thanks for this cool solution.
Ushi

Thanks for this good work.

Oscar

I’m a sharepoint newbie. I installed MOSS 2007 this morning. It works, front end work and administration panel too.
I would try your SP Database Explorer.

When I start it, it ask me SQL Server Name and Database name.

I’m sure where to find these informations.
On the sharepoint administratiion console I found that main database server is : SYRTOS-2\OfficeServers (SYRTOS-2 is the name of my test server), so I set the Sql Server Name with this value and I kept Database name empty.

I have the error message :
System.application.exception : This database structure is not recognized as a SharePoint 2003 or SharePoint 2007.

I think I must set a value for “Database server”, but where could I found this value ?

Thanks.

I am happy that helped you.

Thanks.
Pascal.

thanks a lot!
thanks a lot!
thanks a lot!
thanks a lot!

you are a master in this!

because an electric cut , the master db of my sql server turn down it didn’t answer , so i had to reinstal it and also sharepoint services 3, but i only had content db, and with your powerful app i got back all files of my fellows

I too would like to automate this tool. I got halfway, but once I get to exportmanager and the formaters, I get lost.

I understand you think this is only a last resort tool, but for those of us still running 2003 this would be a great way to allow single file restores.

I would be willing to pay for your time to implement this feature. Please email me.

Thanks!

PS. This tool saved my butt a couple of years ago… thanks so much!

I have implemented the code provided by Amrit into version 1.1.0.3.

This version now export documents with the same directory structure as it was stored into the document library.

All thanks to Amrit.

Pascal.