http://blog.benhall.me.uk/2007/04/sqlparameter-is-already-contained-by.html
Search This Blog
Wednesday, March 24, 2010
Wednesday, March 10, 2010
JFTP::store: Bad response Warning! Failed to move file.
Site > Global configuration > Disable ftp access
Wednesday, February 17, 2010
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user SID (S-1-5-21-573225893-205518295-0000000000-00000). This security permission can be modified using the Component Services administrative tool.
- Search the GUID in HKCR registry..
- 61738644-F196-11D0-9953-00C04FD919C1
- The service name for this key is IIS WAMREG Admin Service
- Load DCOMCNFG, browse to My Computer -> ” DCOM Config”
- Go to the properties of IIS WAMREG
- The permission missing was “Local Activation” permissions for the user .
http://www.cleverworkarounds.com/2007/10/25/dcom-fun-with-sharepoint/
Tuesday, February 2, 2010
The server tag is not well formed
Use single quotes instead of double :)
http://blogs.clearscreen.com/ragc/archive/2004/10/28/525.aspx
Thursday, January 14, 2010
autochk program not found – AUTOCHECK skipping
I resolved it by Start > Run > sfc /scannow
http://www.techspot.com/vb/topic7746.html
http://www.windowsbbs.com/windows-xp/46438-autochk-program-not-found.html
Bad array declarator: To declare a managed array the rank specifier precedes the variable's identifier. To declare a fixed size buffer field, use the fixed keyword before the field type
Wrong Declaration
char CopiedString[];
char[] CopiedString;
Correct Declaration
char[] CopiedString = new char[3];
char[] CopiedString = xyz;
http://dotnetdud.blogspot.com/2008/08/bad-array-declarator-to-declare-managed.html
"One or more field types are not installed properly. Go to the list settings page to delete these fields."
I received this error while using an SPQuery CAML query string. the problem was that I had renamed my Title column in the list to “Document Library Name” and in the SPQuery i was using
query.Query = "<Where><Eq><FieldRef Name='Document Library Name'/><Value Type='Text'>" + this.workflowProperties.List.Title + "</Value></Eq></Where>";
after some research I found out that the internal name of the column was still ‘Title’ so i used
query.Query = "<Where><Eq><FieldRef Name='Title'/><Value Type='Text'>" + this.workflowProperties.List.Title + "</Value></Eq></Where>";
and the error was gone :D
Tuesday, January 12, 2010
The requested URI is invalid for this ftp command
http://www.eggheadcafe.com/community/aspnet/2/60622/ftp-uri-invalid.aspx
http://forums.asp.net/p/1233240/2242751.aspx#2242751
Uri target = new Uri("ftp://ftp.placer.dyndns.org/test.css");
URI formats are not supported.
I was using File.OpenRead(xyzURL) when i received this error. the solution was to use a webclient
‘Access denied’ when deploying VS 2k8 Sharepoint workflow
(I couldnt get a resolution to this error but following is a workaround)
1. Create a directory in the features directory [C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\FEATURES] and drop both the feature.xml and workflow.xml files into the directory.
2. Install the feature on your farm, using the following command line statements
stsadm -o installfeature -name <<name>>
4. Activate the feature to a site collection
stsadm -o activatefeature –name <<name>> -url <<url>>
Replace <<name>> and <<url>> with the actual value
http://www.codeproject.com/KB/WF/sharepointworkflow.aspx?msg=2656569
***EDIT: Strange enough, I added System.Configuration reference in the project for some other purpose; and this error was gone :D
Tuesday, December 22, 2009
Wednesday, December 9, 2009
String or binary data would be truncated.
I was getting this error when i was trying to delete some rows from the table.
Monday, December 7, 2009
Wednesday, December 2, 2009
Tuesday, November 24, 2009
Cannot Find SharePoint Site or SharePoint Server Instance
This problem can occur when the workflow deployment process cannot open the SharePoint site.
Error Messages
-
SharePoint Server not available.
-
Cannot find a SharePoint server instance.
-
Cannot find the specified SharePoint site: <site URL>.
Resolution
-
Ensure that SharePoint Server is running.
-
In the Properties window, ensure that the site specified in the Target Site field is a valid SharePoint site.
-
Examine the SharePoint diagnostic log files. The default location of these log files is drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS. If you cannot find the log files at this location, refer to the diagnostic logging settings in the SharePoint Central Administration Tool. For more information, see the documentation for Office SharePoint Server 2007.
http://msdn.microsoft.com/en-us/library/ee231594(VS.100).aspx