Thursday, June 30, 2011
#
Symptom:
Adding a custom "New ITem Form" to a page in SharePoint Designer 2010. The new form adds properly and configures normally, but when you try to use it to submit a new item, you get this error:
Failed to get value of the "Attachments" column from the "Attachments" field type control. See details in log. Exception message: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)..
Solution:
Follow best practices. :)
This was in our dev environment and I was hiding the out of the box new item form and adding a new (custom) one to the page. The error goes away when you create a new form and stop fiddling with the out of the box pages. Harumpf.
Wednesday, May 11, 2011
#
Problem:
Every night, around 4 AM, the SharePoint temp DB and logs would grow very very large. Size increased by about 60 GB every night, then shrank again. I couldn't figure out why the excessive growth was happening to one of the content datases and the temp database. All research pointed to the search crawler writing to the temp files. These are the steps I took:
- I disabled all crawls
- I disabled all usage analysis jobs
- I disabled any job running at night.
This had no effect. The databases were still growing out of control every night starting at 4 AM even though I had no jobs scheduled at that time. But SOMETHING must still be running...
Issue:
I isolated the issue to one content database that was also growing every night. There was one site in the database that went through a fairly major cleanup and had deleted 60 GB of content in one day from one folder just over 30 days prior.
I looked in the 2nd level recycle recycle bin and the folder was still there - deleted over 30 days previously. The recycle bin should have deleted it during cleanup days ago. It had actually been trying, but not successful.
SharePoint was running the job to delete items from the 2nd level recycle bin, starting the job at 4 AM, writing to the temp db and the transaction logs, then timing out. So, it would not finish the deletion. The entire process would start again the next night.
Solution:
I restored the content from the recycle bin to the site. I went into the library and deleted smaller chunks, instead of one folder. Then, I manually deleted 3-4 GB at a time from the 2nd stage recycle bin during off hours, which flushed the items from the database and lessened impact to users. Problem solved.
I also learned that you can set the schedule of the Recycle bin cleanup via stsadm commands:
To set the schedule of a Recycle Bin cleanup for the Web application use the following syntax:
stsadm -o setproperty -pn job-recycle-bin-cleanup -pv "daily at 15:00:00" -url <site URL>
To view the current setting of the job-recycle-bin-cleanup property, use the following syntax:
stsadm -o getproperty -pn job-recycle-bin-cleanup
Thursday, May 05, 2011
#
Symptom: When trying to publish a page in SharePoint 2010 publishing template, you get this error:
The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator.
Problem:
The State Service is not configured. When you decide to configure everything yourself when installing 2010, the state service can only be installed/configured using PowerShell or the configuration wizard.
Solution:
Configure via configuration wizard:
Go to central admin, click on Configuration Wizards, Launch the Farm Configuration Wizard. Check the box for State Service and deselect everything else. Click on Next.
You can install it with Powershell, which I didn't choose. I was reading that it can be problematic. At some point I will research again and maybe the bugs will be worked out.
To configure the State Service by using Windows PowerShell:
1. Click Start, Administrative Tools, Windows PowerShell Modules.
2. In Windows PowerShell, type $serviceApp = New-SPStateServiceApplication -Name “State Service”
3. Create a State Service database and associate it with a service application, by typing New-SPStateServiceDatabase -Name “StateServiceDatabase” -ServiceApplication $serviceApp
4. Create a State Service Application Proxy and associate it with the service application by typing New-SPStateServiceApplicationProxy -Name “State Service” -ServiceApplication $serviceApp -DefaultProxyGroup
(You can use another proxy group if necessary by changing the DefaultProxyGroup parameter)
Tuesday, May 03, 2011
#
Problem:
FAST Search is asking for the port number of SQL for the install. If it isn't the default, what is it and how do I know?
Solution:
Execute the following query in SQL:
DECLARE @test VARCHAR(15) ,
@value_name VARCHAR(15) ,
@RegistryPath VARCHAR(200)
IF ( CHARINDEX('\', @@SERVERNAME) <> 0 ) -- Named Instance
BEGIN
SET @RegistryPath = 'SOFTWARE\Microsoft\Microsoft SQL Server\' +
RIGHT(@@SERVERNAME,
LEN(@@SERVERNAME) - CHARINDEX('\', @@SERVERNAME)) +
'\MSSQLServer\SuperSocketNetLib\Tcp'
END
ELSE -- Default Instance
BEGIN
SET @RegistryPath = 'SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp'
END
EXEC master..xp_regread
@rootkey = 'HKEY_LOCAL_MACHINE' ,
@key = @RegistryPath ,
@value_name = 'TcpPort' ,
@value = @test OUTPUT
PRINT 'The Port Number is ' + CHAR(13) + @test
Result:
In the messages, you will see this:
The port Number is
12345
Monday, April 18, 2011
#
Symptom:
When trying to use RDP to a Windows Server 2008 machine, the following error message appears:
An authentication error has occurred. The Local Security Authority cannot be contacted. Remote computer: xxxxxxxx
Problem:
The security setting is too high to allow the account to log in.
Solution:
Lower Remote Desktop Security - On the terminal services server, go to Start, right click Computer, click on Advanced System Settings -> Remote Tab -> Allow connections from computers running any version of remote desktop (less secure).
Friday, April 08, 2011
#
Symptom:
I had a solution that was stuck in the deploying state. When I looked at it, it had only deployed successfully on one the the front ends. To solve the problem, I ran stsadm execadmjobs. I have done this multiple times in 2007, but this time I got this message:
The administration service is running so all administration jobs will be run in the timer service.
Problem:
The timer service is set to take care of all admin tasks, so it is telling you that the jobs will run when the timer service is good and ready to kick them off, but until then, just sit on your hands and wait.
Solution:
Stop the admin service, then run the command to execute the admin jobs, then turn back on the admin service. These are the three powershell commands to do this:
- net stop SPAdminV4
- Start-SPAdminJob
- net start SPAdminV4
The first command shuts off the admin service. The second command is the powershell equivalent to stsadm execadmjobs and the third one turns back on the admin service.
Friday, February 11, 2011
#
Problem:
Not exactly SharePoint, but the issue is when setting the %JAVA_HOME% environment variable, Java installs to the Program Files directory by default. The space in the path seems to stop the variable from being read. You get an error.
Solution:
Change Program Files to Progra~1, so the path now looks like this:
C:\Progra~1\Java\jdk1.6.0_23\bin\;
You can type %JAVA_HOME%\bin\javac to test. Output should look like this:
Usage: javac <options> <source files> |
where possible options include: |
Tuesday, February 08, 2011
#
Sytmptom:
You have a list or document library page (allitems.aspx) and you are trying to add a Web part. You get an error message:
Unable to add selected Web part(s). (name of Web part): The file is not checked out. You must first check out this document before making changes.
Publishing features are not turned on and it is not a page that lives in a library accessible by the GUI.
Solution:
Open the site in SharePoint Designer and check out the page. Then, check in the page after modifications are done. It seems like this is just a bug.
Friday, August 06, 2010
#
Symptom:
This Error in the application event logs:
Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
Additional Data:
Current default super user account: SHAREPOINT\system
Solution:
This time, a helpful message in the error itself. Just follow the instructions in the error and use the stsadm command to set the super user account for each Web app.
Symptom:
EventID 7043 Source: SharePoint Foundation
Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.
Problem:
The file drive:\Program Files\Common Files\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\TaxonomyPicker.ascx is badly formed and doesn't compile.
Solution:
You can change the bad syntax of the file. To Fix:
Find the character string , and replace with a comma ‘,’ (without quotes).
Or, you can rename it TaxonomyPicker.ascx_broken. It is badly formed, but the file is never actually used. Thank you to this post for the answer:
http://todd-carter.com/post/2010/05/03/Help-Wanted-Taxonomy-Picker.aspx
Thursday, August 05, 2010
#
Problem:
After a database detach upgrade from 2007 to 2010, you try to do a visual upgrade and get this message:
| |
 |
| |
| Visual Upgrade failed. The default master page for this user interface could not be found at "/teams/xxxxx/_catalogs/masterpage/v4.master". Add the requested master page at this path and try again.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: a4ead41e-8c93-4d9d-ae0e-580902b71714
|
|
Problem:
It is looking for a masterpage that isn't in the 2010 library.
Solution:
In short, add it to the library. To do this:
1. Go to the upgraded 2010 site, and make a subsite
2. Download a copy of the v4.master page. (Site Settings, Galleries, Master Pages)
3. Go to the upper level (or any site where the error is) and upload the copy of the v4.master into the master page gallery. (Site Settings, Galleries, Master Pages)
4. Try the visual upgrade again.
Wednesday, June 02, 2010
#
Symptom:
When configuring incoming e-mail, the e-mails come through just fine if the server name is in the e-mail address:
mylist@servername01.fqdn.com but when you change it to a vanity name mylist@sharepoint.fqdn.com, the message is bounced back and you get this error:
Delivery has failed to these recipients or distribution lists:
test3@sharepoint.fqdn.com
Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
The following organization rejected your message: servername01.fqdn.com.
Problem:
The SharePoint server relay rejects the message because it doesn't recognize the name. You have set it up in Exchange, but you need to set up an alias in the SMTP service on the SharePoint server;
Solution:
Configure an Alias Domain
An alias domain is an alias of the default domain. You can set up alias domains that use the same settings as the default domain. Messages that are received by the SMTP Service for an alias domain are placed in the Drop folder that is designated for the default domain.
To configure an alias domain, follow these steps:
- Start IIS Manager or open the IIS snap-in.
- Expand Server_name, where Server_name is the name of the server, and then expand the SMTP virtual server that you want (for example, Default SMTP Virtual Server).
- Right-click Domains, point to New, and then click Domain.
- The New SMTP Domain Wizard starts.
- Click Alias, and then click Next.
- Type a name for the alias domain in the Name box, and then click Finish.
- Quit IIS Manager or close the IIS snap-in.
Friday, May 07, 2010
#
http://support.microsoft.com/?id=962928
To resolve this issue, follow these steps:
- Stop the Office SharePoint Services Search service. To do this, follow these steps:
- Click Start, click Run, type cmd , and then click OK.
- At the command prompt, type net stop osearch, and then press ENTER.
- Type exit to exit the command prompt.
- Download and install the IIS 6.0 Resource Kit Tools. To obtain the IIS 6.0 Resource Kit Tools, visit the following Microsoft Web site:
- On each server in the farm that has Office SharePoint 2007 installed, follow these steps:
- Click Start, click Run, type cmd , and then click OK.
- Navigate to the location of the IIS 6.0 Resource Kit Tools (default location is: C:\Program Files\IIS Resources\SelfSSL)
- At the command prompt, type selfssl /s:951338967 /v:1000, and then press ENTER.
Notes
- For 64 bit Server, 951338967 is the default ID of the Office Server Web Services certificate.
- For 32 bit Server, 1720207907 is the default ID of the Office Server Web Services certificate. You can check the ID of Office Server Web Services from IIS.
- 1000 is the number of days that the certification will be valid.
- You need to execute the selfssl command on each MOSS Server in the farm which is running a "Office Server Web Services" site.
- SharePoint partly uses SSL name resolution in the background between farm servers, which users generally do not need to be aware of.
- Start the Office SharePoint Services Search service. To do this, follow these steps:
- At the command prompt, type net start osearch, and then press ENTER.
- Type exit to exit the command prompt.
- Download and install the following update to the .NET Framework 3.5 SP1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
959209 (http://support.microsoft.com/kb/959209/ ) An update for the .NET Framework 3.5 Service Pack 1 is available
Tuesday, March 09, 2010
#
Symptom:
After installing SharePoint Learning Kit successfully, (http://www.codeplex.com/SLK), everything works except that the SCORM package (a ZIP extension) is opening as a ZIP file instead of a course. You get the normal ZIP message "Do you want to open or save this file?"
Problem:
The package is zipped at the upper folder level and does not create a manifest that allows SharePoint to recognize it as a SCORM file instead of a ZIP file.
Solution:
Add the contents of the course to the ZIP, not the outer (uppermost) folder. This creates a ZIP file that SharePoint can recognize as a SCORM package.
Saturday, February 20, 2010
#
When trying to enable Enterprise Features, the page comes up with a "Failed!" result. (No kidding - they added the exclamation point.) When you try to activate it again, you get this message:
An existing request to enable the Enterprise feature is in progress. To check the status of this request, go to the Timer Job Status page in Central Administration Operations and check the status of the Office Server Enterprise Features Upgrade Job.
When you check the status, it also says failed.
To fix this, I just restarted the Timer Service on each server in the farm. This kick-started the process and the upgrade job finished with success.
Wednesday, February 17, 2010
#
Thursday, January 07, 2010
#
Symptom:
Your account is the farm administrator and has been added to the policy for the SSP, as well as the site collection owner, but when you click on User Profiles and Properties (in the SSP under User Profiles and My Sites), you get "Access Denied"
Problem:
The account has not been added with permissions to manage My Sites.
Solution:
Click on Personalization Services Permissions (in the SSP under User Profiles and My Sites). Add the account and give Manage User Profiles permissions.
Monday, January 04, 2010
#
Symptom
The stock ticker Web part found here: http://www.codeplex.com/svstockticker is properly installed and rendering. But instead of displying the stocks, this message appears: "Unable to contact the yahoo finance web site." You are able to navigate to the yahoo site just fine, so it is up and running, but just not able to connect through the Web part.
Problem
I found a clue to the answer from Scott Vintinner on one of his blogs.
He said, "That message usually means that the web server is unable to access the Yahoo web site. The Sharepoint web server downloads the data file directly from the Yahoo website (the client only downloads the chart images from the yahoo web site). Check with your firewall people to make sure that your server can access the Internet. If you use a proxy configuration, you'll need to modify the web.config file to accommodate that (I'm not sure of the steps)."
Solution
I changed the web.config in the virtual directory for the Web application. The default location is here: C:\Inetpub\wwwroot\wss\VirtualDirectories\Your_SharePoint_Site.
1. Make a backup copy of the web.config.
2. Change this line:
<defaultProxy>
<proxy autoDetect="true" />
</defaultProxy>
to:
<defaultProxy>
<proxy autoDetect="false" />
</defaultProxy>
3. Save the web.config
After this change, I was able to see the stock in the Web part without an issue.
Sunday, December 27, 2009
#
Symptom:
When you try and edit the crawl schedule in MOSS, you get an access denied:
Access is Denied (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))
Problem:
The wss_wpg doesn't have read/write permissions on the Windows/Tasks folder
http://support.microsoft.com/default.aspx?scid=kb;en-us;926959&sd=rss&spid=11373
Solution:
1. Change attributes of Tasks folder by typing this in a command prompt:
attrib -s c:\windows\tasks
2. Restart Windows Explorer.
3. Add the wss_wpg account with read/write permissions to the permissions of the folder
4. Change the attributes of the Tasks folder back to a system folder:
attrib +s c:\windows\tasks
- Navigate to the site directory.
- Backup web.config.
- Open web.config.
- Switch Custom Errors off. Search for “customErrors” and set the value to “Off” instead of “On”. You can also set the value to “RemoteOnly” to troubleshoot a production issue.
- Enable CallStack. Search for “CallStack” and set the value to “true” instead of “false”.
- Save web.config.
Tuesday, December 22, 2009
#
Problem:
When adding a server to the farm, the "Windows SharePoint Services Web Application" is stuck in a starting state
Symptom:
In Central Admin, Services on Server, status is "Starting"
Solution:
From the command line:
stsadm -o provisionservice -action start -servicetype SPWebService
You will get this:
Operation completed successfully.
If this is a Web service, IIS must be restarted for the change to take effect.
To restart IIS, open a command prompt window and type "iisreset /noforce".
Service is now started and it is possible to start other services successfully.
Problem:
SharePoint Configuration Wizard stuck at task 8 of 9
Symptom:
This appears in the upgrade.log file:
[SPManager] [DEBUG] [12/22/2009 1:56:15 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds
[SPManager] [DEBUG] [12/22/2009 1:56:25 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds
[SPManager] [DEBUG] [12/22/2009 1:56:35 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds
[SPManager] [DEBUG] [12/22/2009 1:56:45 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds
[SPManager] [DEBUG] [12/22/2009 1:56:55 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds
Solution:
Set the following services to manual startup and shut them off:
World wide web service
Microsoft Single Sign-on Service
Windows Sharepoint Services Search
Restart spadmin and sptimer services
If needed: Command line with C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>psconfig.exe -cmd upgrade -inplace b2b -wait -force
Friday, December 18, 2009
#
Syntax
stsadm -o addwppack
-filename <file name>
[-lcid] <language>
[-url] <URL name>
[-globalinstall]
[-force]
[-nodeploy]
stsadm -o addwppack
-name <Web Part name>
[-lcid] <language>
[-url] <URL name>
[-globalinstall]
[-force]
Friday, December 11, 2009
#
Symptom: Can't build/deploy WSP in Visual Studio
Error message: cablib compress error: could not flush cabinet
Problem: In the file structure, the WSP has a property of Read-Only. It can't create a new WSP because it can't overwrite the file.
Solution: Go into the file structure where the WSP gets built and right-click for properties. Uncheck Read-only and try to rebuild/deploy.
Thursday, December 10, 2009
#
When preparing to install SharePoint, ASP.NET v2.0.50727 must be set to a status of allowed in IIS Web Service Extensions. If this item is not in the list in IIS, navigate to:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727> or
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727> for 64 bit
At the command prompt type: aspnet_regiis - i
Go back into IIS Manger and it will show in the list and you can set it to a status of Allowed.