Sharepoint gone horribly wrong suddenly

[zag]

Came in this morning to find a few reports of things not working on Sharepoint 2010.

 

Basically when I try to upload a document it says

 

 

"The URL is invalid, it may reference a non existing file or folder"

 

I've tried rebooting the sharepoint server but no luck

 

Any ideas how to troubleshoot this?

 

EDIT: Got it I think. SQL server is producing this error

Log Name: Application

Source: MSSQL$SHAREPOINT

Date: 16/02/2011 09:43:28

CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.

Edited February 16, 2011 by zag

[HMCTech]

SQL Express?

[zag]

Yep just worked out I did a stand alone install when I created it which automatically installs sql server compact edition. I've got 2008 SQL enterprise installed on the server its just not using it!

 

Anyone know how to migrate sharepoint dbs?

[jamesb]

Here you go - Move all databases (SharePoint Server 2010)

[apearce]

you need to install full SQL Server as your limit to SQL Express is full.

 

You can do this 2 ways

 

1. Export your SharePoint environment, don't forget to include security permissions and the import it into a completely new SharePoint farm.

Export a site, list, or document library (SharePoint Server 2010)

 

2. Connect your SharePoint farm to a new SQL Server and remove the connection to the existing database. The connect SharePoint using database attached.

 

If it was me - I would do option 3

 

3. Create new farm that is not standard install. Build the farm with just the service application you require and then do a database attached to the new farm.

 

A.

 

 

 

Came in this morning to find a few reports of things not working on Sharepoint 2010.

 

Basically when I try to upload a document it says

 

[ATTACH=CONFIG]9477[/ATTACH]

 

"The URL is invalid, it may reference a non existing file or folder"

 

I've tried rebooting the sharepoint server but no luck

 

Any ideas how to troubleshoot this?

 

EDIT: Got it I think. SQL server is producing this error

[zag]

Is it not possible to upgrade the SQL server and keep the same Database instance?

 

I saw this blog post but it relates to sql server express not compact edition.

[zag]

I'm so confused after hours of googling I don't seem to be any closer to a way of fixing this.

 

From what I can tell, I have "compact edition 3.5" of SQL installed(not express) and all my data files are in:

 

C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA

 

There doesn't seem to be any way to connect to this with sql server manager and therefore I can't export it.

Edited February 17, 2011 by zag

[jamesb]

You could just stop all services, copy the files, import them into a new instance, cross your fingers and hope for the best?

[zag]

Gave up in the end, Re-installing sharepoint on a new server from scratch seems to be the safest option.

 

This time I won't select a "stand alone" install.

[jamesb]

This time I won't select a "stand alone" install.

 

They really, really need to just take that option out. I've never seen a purpose for it (excepting installs on dev machines, but even then a farm works fine).

[zag]

They really, really need to just take that option out. I've never seen a purpose for it (excepting installs on dev machines, but even then a farm works fine).

 

Yep, it makes no mention that there is a 4gb limit or that SQL server compact is going to be installed. I had SQL 2008 enterprise installed before but the installer just ignored it.

 

And even worse Microsoft don't provide an easy upgrade route, I've read hundreds of posts online over the last few days of people making exactly same mistake. Its simply not realistic to start detaching databases on my main live SP install.

 

Things like this in IT drive me nuts.

 

Ok rant over

[jamesb]

Of course, if it was easy none of us would have jobs.

 

I've actually got a similar problem. There's a live, hosted site which is in use at the moment, and is set up as a standalone which can't be expanded. Given the amount of usage the system will be getting once the full solution's deployed, it would simply snap under the strain. The solution we're going for is to assign it to someone who can keep it limping along until an actual enterprise solution is finished, at which point it gets scrapped in its entirety and everything comes in-house. Some opposition to this idea at the moment, so I may have to use your story as an illustration of why trying to upgrade is more trouble than it's worth.

[zag]

Fixed it!

 

Blogged about it here

 

Sharepoint 4GB limit - Blogs - EduGeek.net