For SharePoint 2007 or WSS it is nearly impossible to install on something other than Windows Server ..there were some articles explaining how to install WSS 3.0 on windows 7 by using some tools but honestly, I try and I could not be able to get it work.
When I find out that SharePoint Foundation (the new name of WSS in SharePoint 2010 platform) could be installed on Windows 7 I was very happy. At last I can use my own machine for development purposes without having to use any virtual machine.
What you need is explained detailly over here:
http://msdn.microsoft.com/en-us/library/ee554869.aspx
Good luck!
Salı
How to keep Workflow History data more than 60 days in SharePoint
I am not sure if it is officially declared by Microsoft or not, but SharePoint is set to delete/purge workflow history from database after 60 days. That means you can't find anything more than 60 days old in Workflow history list by default setting.
If you are using custom developed workflows that could be annoying because you'll have to keep approval workflow info vs. more than 60 days according to your company policies etc.
There is a simple way to prevent this behaviour. Just log on to Central Administration and Go to Timer Job Definitions on Operations page.
Find the "Workflow Auto Cleanup" timer job that belongs to the web application you want to preserve.
Disable it, thats it..
If you are using custom developed workflows that could be annoying because you'll have to keep approval workflow info vs. more than 60 days according to your company policies etc.
There is a simple way to prevent this behaviour. Just log on to Central Administration and Go to Timer Job Definitions on Operations page.
Find the "Workflow Auto Cleanup" timer job that belongs to the web application you want to preserve.
Disable it, thats it..
Cuma
Create New item in a custom list leads to "Unknown error"
Last week we had a nasty problem. In a custom list of a custom site, new items were not getting created. The "new form" aspx was customized as well. When you click new item (it was a custom content type also) SharePoint gave a big nice "Unknown error" screen.
we discovered two anomalies:
1. the first thing I got suspicious was the item count. Sharepoint hard limits are really annoying..I was right about getting suspicioous over item count, we deleted some of items from the list, the error vanished! But the list had to grow..
2. When you sign on as the "Site Collection Administrator" magically, you have no errors, everything worked fine. It does not even work when you have the full control permission level on list or site..Just being in "site collection administrators" group keeps the error away.
We dig the ULS and found out that kind of errors:
"Application error when access /_layouts/unit/forms.aspx, Error=Must declare the table variable "@_scopeTbl". Must declare the table variable "@_scopeTbl". Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at..........................."
So after a quick googling, I found that cumulative update: http://support.microsoft.com/kb/973410
(Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package)
Although it seems to be curing the render failed error messages.
I never liked patching my farm on place, if we have custom development on it .. I usually do install a new farm, attach content db, and upgrade. Then re-deploy the custom solutions on it...
I did this in order again and the Cumulative update really worked for the problem but unfortunately, It caused other things to crash... Now some of the custom built workflows are not working and its a complete pain to seek a way to fix them.
we discovered two anomalies:
1. the first thing I got suspicious was the item count. Sharepoint hard limits are really annoying..I was right about getting suspicioous over item count, we deleted some of items from the list, the error vanished! But the list had to grow..
2. When you sign on as the "Site Collection Administrator" magically, you have no errors, everything worked fine. It does not even work when you have the full control permission level on list or site..Just being in "site collection administrators" group keeps the error away.
We dig the ULS and found out that kind of errors:
"Application error when access /_layouts/unit/forms.aspx, Error=Must declare the table variable "@_scopeTbl". Must declare the table variable "@_scopeTbl". Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at..........................."
So after a quick googling, I found that cumulative update: http://support.microsoft.com/kb/973410
(Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package)
Although it seems to be curing the render failed error messages.
I never liked patching my farm on place, if we have custom development on it .. I usually do install a new farm, attach content db, and upgrade. Then re-deploy the custom solutions on it...
I did this in order again and the Cumulative update really worked for the problem but unfortunately, It caused other things to crash... Now some of the custom built workflows are not working and its a complete pain to seek a way to fix them.
Kaydol:
Kayıtlar (Atom)