I am new to sharepoint,i have created documentset and i have added few documents, if i change the status of the document to 'xxx',then i need to create copy of that documentset.(ex:original documentset name is test,after changing the status i have to create test_review.
Well that isn't the way you should do it in SharePoint. "Copies" aren't meant to be created, as SharePoint is no FileSystem. You should integrate Versioning and create Minor or Major Versions with the ability to be approved.
Of course you could create a copy (DON'T DO IT) but that would be against the principles of management of documents in SharePoint. You just should have just one instance of every document, best with a global ID. Changes should be maintained due by versioning.
If you still like to create a copy (DON'T DO IT), then you could build a workflow and create a copy (DON'T DO IT) or you could build a solution with an event (DON'T DO IT).
The only reason I see for creating copies is a public archive with a documentset which is build of several documents by automation. But just a copy of an existing documentset should be handled by versioning: There is a public (major) version to read and a internal minor version to change.
SharePoint provides the options to prevent dublicates, which wasn't possible in the filesystem! Use them. Don't create copies!!! (think yourself a hundred more exklamation marks at this point)
It's not easy to answer that without knowing how many people will access and how they will work with sharepoint. It's like asking what engine you need if you buy a new car without knowing your driving style and if you like to pull a trailer.
You need (for SharePoint 2010):
- Windows Server 2008 R2 / 2012
- Optional (but usefull) SQL-Server 2008 R8 / 2012
- Optional MS Office Plus (if you want to provide office services)
- A connection to AD
For SharePoint 2013 you should run Windows 2012 and SQL-Server 2012
Hardware for good working for up to 150 workers:
- 4 Core
- 8 better 16 GB RAM
- 2 Core +
- 16 GB RAM
You should perform a farm installation even if you install everything on one machine.
This is my first question on the forum so feel free to move/delete/refer as necessary.
What's happening is that when you access our new Sharepoint site in our head office, and your security settings are correct, you are prompted to log in once when you open the site and then you can continue on opening other pages and documents with no additional requests for credentials. Totally normal.
Now, if you use an identical computer in another office in a different city (so we have the same credentials, OS, security settings), you are periodically and seemingly randomly asked to log in multiple times while browsing the site. In some cases, you will have to enter your credentials 10 times, one right after the other, before you can continue viewing a page or opening a document. It is extremely disruptive.
Also, if you take that same, identical computer home or to a hotel and try to log on to our Sharepoint site, you'll have no problems. It's like you never left the office. You'll be prompted to log in once when you enter the site and then you won't see the login prompt again.
The Sharepoint machines are located in our head office and the remote offices access the Sharepoint site through a VPN tunnel. The remote office can ping both the main Sharepoint site as well as the the domain controller with no problem.
Has anyone even encountered this problem before? Any and all suggestions will be very welcome!
Well, that might be the answer. I have several VMs with different SharePoint installations and on some without Keberos there are Problems. Kerberos is standard nowadays, I think you are using it in AD so you might should activate it in SharePoint.
VPN settings I will have to look into, but I know for a fact that the IE settings and updates are the same. We've actually moved one of the managers (and her laptop) from one office to the other, and she is fine here but on the same laptop in a different office she has problems. I was even able to remote in and do some testing, it was very intermittent.
She says things were fine while she was in the hotel though...
And the weird thing is that it's not just the one office but all the field offices that have this problem.
It has to be the firewall or VPN; we're running out of other options!
I will keep you posted.
So we ended up contracting an external netowrk guy to fix something completely unrelated. In order for him to dial-in to a computer at one of our other sites to do maintanence we had to temporarily turn off the anti-virus on the router. Guess what? People could log into SharePoint with no problems while we had the anti-virus turned off. Looks like the auths where getting picked up by the anti-virus on their way back out to the client. Go figure.
Anyways, we've reconfigured our antivirus and everyone is happy.
I don't know how extensive you want your re-theming to be. However if it could be CSS-only you could use this approach:
Store the CSS files for the different themes in the Style Library or in 14 Hive.
Create a list/table that stores the user and their chosen theme.
Write a feature and custom application page to allow the user to change their theme.
Write a control that does a lookup on the list against the current user and obtains the a reference to the corresponding CSS file in the Style Library or in 14 hive. The control would then output the CssRegistration and CssLink controls to the page for this file.
Add this control to the master page so it executes on every page (caching should be added).
I can't see why this wouldn't be supportable by Microsoft as you're only changing CSS.
I´ve the Reservation Webpart in my WSS 2007 Site. In this Year I can insert some reservations at the same Time or Time overlapping for different rooms. In 2013 a error ocurred
"The following reservation conflicts with the desired reservation." What can I do?
I am going to create new shared document which will helps user can share the documets by using this site.And we already have SQL server 2008 & Visual Studio 2008 in using.That using SQL server 2008,VisualStudio 2008 is enough or we nee to install in saparate server.Can you please mensition the Hardware and Software requirements for creating sharepoint document shareing(Shared document).
Can you please mensition the Hardware and Software requirements for creating sharepoint document shareing
You should install a SharePoint FarmServer (even if you only have one Server, because you can then add other servers, if you need them).
Depinding on how many users you have a good start would be 4 Cores with 8 better 16 GB. You can also use VMs if you like to, it's a good way, cause you can easily backup them.
SharePoint 2010 and SQL-Server 2008 or SharePoint 2013 and SQL-Server 2012 are good combinations.
You only need Visual Studio if you want do build Solutions, but it's better not to run Visual Studio on production Servers, install another Server.
Running with 2 Custom master pages that previously worked on Server 1
Now a new server is established and "Invalid viewstate" now occurs – It's the mngfield.aspx that is involved
I can create a column on list or document library but can’t delete it again.
No changes has been made in the master pages at all.
If I change the custom master page to standard master page there’s no errors.
The URL when the error occur is:
The ULS log contains:
w3wp.exe (0x0c9c) - Thread: 0x0F78 - Level Medium and Unexected on the tkau
the ULS Eventid is:
Last Visit: 31-Dec-99 18:00 Last Update: 26-Sep-16 15:42