When you are using multiple companies and login thru Web Clock, sometimes, you may not see the companies drop down and may see the above error.
You need to make sure Multi Company Module is loaded.
And also make sure the Auto Update is done for Web Clock.
To do the Auto Update for Web Clock, type /AutoUpdate30/Login.aspx next to the Web URL and click OK. Select the Company from the Drop down and user ADMIN login.
Click on Update, Accept the License, again click on Update.
Click on Exit once the process is completed.
Now you will be able to see Companies Drop down when logged in as USER and MANAGER.
Microsoft Office SharePoint Server 2007 includes a very powerfull tool the Stsadm, stsadm is for command-line administration of Office SharePoint Server 2007/Moss 2007 you can use this sharepoint 2010 also. it can be used for server and sites stsadm can be used by command line or by using batch files or scripts. There are certain operations and certain parameters that are only available by using theStsadm command-line tool.
Where the STSADM is Located
Stsadm is located at the following path on the drive where SharePoint Products and Technologies is installed: %COMMONPROGRAMFILES%\microsoft shared\web server extensions\12\bin. You must be an administrator on the local computer to use Stsadm.Many a times people think of running stsadm.exe commands from any command prompt. So here is the way:
1. Open command prompt 2. Type in the following command: @set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% (This Command does not work on WSS 2.0) In WSS 2.0 Try CD C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN and run the below Commands. 3. You can now run the stsadm.exe commands from anywhere in the command prompt _________________________________________________________________________________
To get the IDs of the Solutions use the below Command
Make sure all deployments are set to DEPLOYING before stopping the services. MY ENVIRONMENT Command prompt, run as Admin on WFE and SQL if you are running SSRS integrated mode. Stop the SharePoint Admin Service Stop the SharePoint Timer service 1) Run stsadm -o execadmsvcjobs on your CA server. 2) Run stsadm -o execadmsvcjobs on all the farm members that have stsadm. 3) Restart the Timer Service on all farm members. 4) Restart the SharePoint Admin service That should fix it.
Managing permissions in SharePoint is a complex and often difficult to understand by end users. In addition, features for managing permissions on a site are splitted on several screens and must access on each item to finely manage the associated rights. When the site is important, it quickly becomes difficult to obtain an overview of permissions and each change creates a lot of work.
This version works with WSS 3.0/MOSS 2007 and Sharepoint 2010 Functions
This tool aims to bring together on one screen, most of management capabilities of permissions for an entire site:
- Overall display permissions for groups on the Sharepoint libraries and website pages
- Adding, modifying, deleting permissions with a few clicks without having to go through a lot of screens (using JQuery)
- Export as an Excel table permissions
- Copy permissions between lists and pages
Planned on future version :
- Import / export permissions as XML (very useful in cases of misuse by the user) in order to quickly restore a configuration permissions
If you are looking for the SharePoint ULS Logs, the default path log locations are below:
For SharePoint 2010: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Logs
For SharePoint 2013: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Logs
Optionally, if you wish to change the location of the ULS logs, you can do so in Central Administration:
In Central Administration, click on Monitoring
You can then click on "Configure diagnostic logging" to alter the path to the diagnostic Trace Logs
To alter the usage logs, you can click on "Configure usage and health data collection" and alter the path for the logs under Usage Data collection Settings.
Now, if you wish to view and actually MAKE SENSE of the ULS Logs, then you will want to use one of the various ULS Log Viewers that are available for download:
The ULS Log Viewer that you choose is largely a matter of personal preference, but it seems that the CodePlex projects seem to provide more functionality than the ULS Log Viewer provided on the MSDN Code site.
The Central Admin URL should be part of Trusted Sites. Otherwise, many features will not work properly.
Go to Central Administration > Application Management > Check Services Enabled in this Farm Clear the Errors logged here.
Once all the Errors are cleared in the above screenshot, 1. We need to create New Web Application (Root Web App). 2. We need to create a SSP (Shared Service Provider) for the farm. If you don't see any other errors while going thru the process, this will help you to get rid of the above message.
Error Messages: Your changes could not be saved because this SharePoint Web site has exceeded the storage quota limit. You must save your work to another location. Contact your administrator to change the quota limits for the Web site. You see the below error when you try to upload the Files to a Document Library.
You see the below error while trying to drag files in the Folder opening the Library with Windows Explorer. "Error 0x8007050F: The requested file Operation failed because the storage quota was exceeded. To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator."
You see the below error message while working with Workflows.
Solution:
Run this query on all the content databases : get the site which has the Quota limit set.
SELECT s.DiskUsed, s.DiskQuota, w.FullUrl from webs w join Sites s on w.SiteId = s.Id where s.DiskUsed > (s.DiskQuota * 0.9) and DiskQuota != 0
Make a note of the output of the above query.
Run the following command and make sure what is the quota limit on the site collections on individual web applications and check the Quota Size:
"The workflow name is used elsewhere on this site. Please choose another name." Problem:
I had a list that implemented ABC workflow, but I deleted this list without remove it. Could you tell me how can I import ABC workflow with the same name? While importing a workflow, If you receive a message: "The workflow name is used elsewhere on this site. Please choose another name". The list is really deleted. Checked in the bin + the admin bin.
Solution:
Suggestion from Nintex Support: There is a hidden list that contains the workflow definition files. You may need to remove the relevant folder (with the workflow name) to remove the workflow completely.
If your site is http://devtest.dev.com/sites/devtest/
the URL would be http://devtest.dev.com/sites/devtest/NintexWorkflows/
Please note after deleting the folder name with problematic workflow name it will be removed completely and not be able to be recovered unless you re import and publish the workflow.
You may also find the following document of interest
Nintex feature is enabled at Site Collection Features and Site Features but still when you go to Workflow Settings of List or Document Library you are unable to see the Nintex workflow menu thru Workflow Settings.
Work around Solution:
Add the below part to the end of the URL after Sites or Lists or Libraries. Use the the ListId of the List or Doucment Library for which you want to go to Nintex Workflows Gallery. "_layouts/NintexWorkflow/WorkflowGallery.aspx?ListId={7C1FC2A8-27B8-4730-ACD1-D269C53ABCC1}" This will take you to the page where you can see the option to view the existing workflows and create new workflows (as shown below).
For Example: https://dev.devsp.com/sites/corp/test/Nin_test/_layouts/NintexWorkflow/WorkflowGallery.aspx?ListId={7C1FC2A8-27B8-4730-ACD1-D269C53ABCC1}
Fixing "User Cannot Be Found" in SharePoint 2010 Workflow Settings *****Do not delete and try to republish the workflows after deletion. This will cause many issues and the related Workflow Tasks from the "Workflow Tasks" library will get deleted automatically.***** SharePoint Designer Workflows We started getting this error overnight on our SharePoint 2010 farm. Workflows stopped working, we couldn't republish list workflows, and we couldn't access the Workflow Settings page for any list or library on the entire site collection. The following error would appear:
"User Cannot Be Found"
Opening SharePoint Designer at the site collection level, we discovered that the Globally Reusable Workflows and Reusable Workflows were owned by user accounts that had been deleted. In order to fix this we used SharePoint Designer to open every workflow and clicked Publish with a static user account (i.e. the Farm service account or App pool service account). After republishing, all started working again. ______________________________________________________________________________________________ Files
However, it seems as though files stored under the OLD profile in SharePoint do NOT automatically get updated with new owner settings when this happens. Again, in our case, I was trying to run the Copy To SharePoint on files uploaded last April, before the change. NONE of them would copy; all would fail with the above error string. Yesterday with Nintex Support on the phone, we tried an experiment by downloading and re-uploading the affected files. Once that was done, they could be copied without error.
This post is just to make you all aware that IF you have made any AD profile changes like the one here, it *may* cause issues with the Copy to SharePoint action.
You can resolve the issue using SharePoint Designer. You need to run the SharePoint Designer with the account listed in Farms Administrator & Site Collection Administrator Groups.
You can also use Command Prompt to start the SharePoint Designer using the below Command C:\>runas /profile /user:dev\devacct "C:\Program Files (x86)\Microsoft Office\Office14\SPDESIGN.EXE" Enter the password for dev\devacct:
When you see the above error while you are using Nintex Workflows, you need to use SharePoint Designer and go to the location >> sites/corporate/_catalogs/wfpub/
Click on "Approval - SharePoint 2010", you will see the below listings. check in and check out the item for which you see the username which doesn't exist (found that the out of the box user was set to a claims based format e.g. "0;#id")
After checking in the item, REFRESH the page, you will see the sign changed after which the workflows started working.
Check all the root Site Collections and clear the usernames which has issues.
Reset and Fix Incorrect or Wrong Password for Windows XP Mode (XPMUser)
Log On with Default Administrator Account
It’s possible to try accessing Windows XP Mode with the default administrator account named “Administrator”, which has been made to only display in Safe Mode. By default, there is no password for Administrator account, so it can be used to reset the password of the password of other accounts.
To do this, please perform the steps below:
On Windows XP Mode window, click on Tools -> Disable the Integration Features.
Restart the Windows XP Mode.
When the Boot Menu appears at startup, press F8.
Note: Keep pressing the F8 key until the Windows Startup menu appears.
On the Windows Advanced Options Menu, select Safe Mode and press ENTER.
Log into Windows by using the Administrator account and password.
Note: The password is blank by default unless you already set a password.
After logging into Safe Mode, click Start, go to Run, type in nusrmgr.cpl and press ENTER.
Choose the user you want to modify and Click Reset Password.
Set a new password.
Click Advanced tab, Click Advanced button.
Click Users.
Choose the user you want to modify in the right pane. Right it and Click Properties.
Check and tick the box of Password never expires.
Click OK.
Quit the settings and restart Windows XP Mode to the normal mode.
When log on to Windows XP Mode, remember to check the box Remember my credentials so that you no need to enter the password again.
I recently had an interesting issue where we were getting the following errors accessing the User Profiles and properties link within SSP.
“An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.”
Notice in the below picture that the schedule fields are blank.
When accessing “Configure Profile Import”, you will see the following error:
An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.
Also, within the Configure Profile Import page, you will see the following error within Incremental Import Schedule & Full Import Schedule:
“Unable to obtain schedule information. Please verify that the job server is up and connected to the farm.”
As a result, profile imports are unable to be scheduled.
This can happen when one of the hidden SSP timer jobs is deleted via pwoershell command (stsadm –o deletessptimerjobs) or accidentally while mis-handling the server re-boot hierarchy. Specifically in this case, the User Profile Incremental Import Job timer job was missing accidentally while mis-handling the server re-boot hierarchy.
You can run the following from the bin directory to validate the missing one of the SSP timer jobs.
In this particular case, the User Profile Incremental Import Job was missing. Unfortunately, the only supported resolution is creating a new SSP or restoring the SSP from backup. I've seen some external public documentation suggesting a fix which includes directly editing the associated SharePoint SSP database. Please be aware that any direct edits to the database is strictly unsupported by Microsoft.
2. Update the ServerName, DatabaseName, Username and password correctly.
Open the TCP Client and verify that you are connected to correct database. You can see the server name in the right -down corner.
_______________________________________________________________________________ Below are the settings for Client Edition of the Time Clock Plus for Users.
Open the TCPCONN.XML existing in C:\Program Files\TimeClock Plus 6.0 using Notepad.
On Site Collection, go to Site Actions >> Site Settings.
Under User Permissions, click on People and Group. On the default Group, go to Settings >> List Settings.
Open the List view and make it default. You can also add more columns like Email.
You can see the List Settings, when your Account listed "Site Collections Administrators".
Upload the HTML script file to a document library on your site. As you can see in the screen shot below, I uploaded my file to a document library named Site config files. It doesn't matter what document library you use to store your file, but make sure all site users have at least read-only access to the library you use. This will ensure the HTML script file can be accessed to render the color coding you’re going to set up.
Validate that the SharePoint list or document library that you want to color code is set up with a Priority field with the following basic settings. (Note that these settings come with the out-of-the-box Priority site column, which you can add to your list or document library.)
Copy the formula provided for your desired formatting. In my case, I’m looking to implement a traffic light indicator so I copied the following formula:
Add a new calculated column to your SharePoint list. Paste the HTML formula string you copied into the new column’s Formula field. Click OK to save your changes.
When you return to your list view, you’ll see your new calculated column displaying with <DIV> tags. Not very attractive.
To correct this issue, we’re going to add our HTML script to the page. Click on Site Actions > Edit Page.
Click Add a Web Part and add a new Content Editor Web Part to your page.
Move your new Content Editor Web Part (CEWP) to the bottom of the page. You need it to display below your list view web part.
Click on the CEWP’s open the tool pane hyperlink.
When the web part configuration panel appears, place your cursor in the Content Link field and enter the location where you stored your HTML script file. Click OK to save your changes.
That’s it! Your formatting is applied and your page should now display your new color coded field. Here’s a screen shot of my finished view, complete with a Priority Level column that displays red, yellow and green traffic lights that correlate with the priority level of each help desk request:
Now that you've set up color coding on one list view, you can continue adding more color coding to this view or add color coding to other views. Note that you will need to add one CEWP to each list view page that you want to color code. There is no limit, however, to the number of calculated columns with HTML encoding you can add to your list.
SharePoint 2010 setup
Validate that the SharePoint list or document library that you want to color code is set up with a Priority field with the following basic settings. (Note that these settings come with the out-of-the-box Priority site column, which you can add to your list or document library.)
Copy the formula provided for your desired formatting. In my case, I’m looking to implement a traffic light indicator so I copied the following formula:
Add a new calculated column to your SharePoint list. Paste the HTML formula string you copied into the new column’s Formula field. Click OK to save your changes.
When you return to your list view, you’ll see your new calculated column displaying with <DIV> tags. Not very attractive.
To correct this issue, we’re going to need to modify this new calculated column. Open your site in SharePoint Designer 2010.
Click on Lists and Libraries in your SharePoint Designer 2010 navigation bar. When the list of your site’s document libraries and lists display, click on the list or document library we’re working on.
When the list or document library details page displays, look for and click on the name of the view you’re applying color coding to. In my case, I am updating the All Issues view.
Once your view opens, click on of the fields that are displaying those ugly
tags. Notice that the <xsl:value-of> tag in the bottom right-hand corner of your screen lights up in yellow once your field is selected.
Hover over the <xsl:value-of> tag until a black drop-down arrow appears. Click on the drop-down arrow and select Edit Tag…
A dialog box will pop up with the following text: Place your cursor between the last quotation mark and the closing > bracket. Now type the text disable-output-escaping=“yes”
Your Quick Tag Editor box should now read like this:
Click on the Quick Tag Editor box’s green check mark icon to save your changes. Your SharePoint Designer page will refresh and your color coding will appear!
Click File > Save to save your changes.
That’s it! Your formatting is applied and your page should now display your new color coded field. Here’s a screen shot of my finished view, complete with a Priority Indicator column that displays red, yellow and green traffic lights that correlate with the priority level of each help desk request:
Now that you've set up color coding on one list view, you can continue adding more color coding to this view or add color coding to other views. Note that you will need to modify the <xsl:value-of> tag for each column you want to display in HTML format. There is no limit, however, to the number of calculated columns with HTML encoding you can add to your list.
