In SharePoint 2010 once I had found a lot of errors in time of execution or publishing workflow processes: "(-1, -1) Type System.CodeDom.
(read more...)
Junior developer created some tools which packed to zip-archive some rendered files. He used for this DotNetZip (Ionic.Zip) library. Everything worked fine until today. But today, when users users tried to open zip-file, they've got the error "CRC has failed, the file is corrupt".
(read more...)
I used Advanced Workflow Actions for SharePoint Designer 2010 from iLoveSharePoint for Workflows in SharePoint site. And one of used by me activities was "Execute PowerShell Script Action".
I have copied exported site to another farm and tried to restore. After executing of cmd-let for restoring spweb (Import-SPWeb -Identity http://spdev/forums/ -Path D:\Backups\forums.bak) I've got an error:
Import-SPWeb : Could not find file 'C:\Users\spadmin\AppData\
Load test allow to understand how many users at once your server and application can process at once. Visual studio 2013 allows you to imitate user action and as robots, so and with human-like behavior.
My post yesterday was about how to get to results of load test. Now I realized that I still hadn't posted about how to create web test and load test in Visual Studio 2013. In Visual Studio 2013 Professional it's rather easy to do – you don't need to install add-ons or plugins, everything is already included.
While removing Site Content Type you got the error that "The content type "My Content Type" is part of an application feature". The fix is rather easy and simple.
Usage "Application configuration file" is very good in creating simple applications. It's very good to store in it values like path, string for database connection or something like this. I use it for a long time. But not so long ago I have noticed that Studio highlights string where configuration file used: (read more...)
Managed metadata is very good and powerful tool in SharePoint. But it has some not very comfortable specialties during migration data from one farm to another, for example, from test environment to productive. You can export your managed metadata from one site and import it into another one. But here's the problem that each termset and term has its own GUID. After you import managed data into the new farm, new GUID’s will be assigned to managed data items.
In SharePoint timer job history I have noticed that there's the error in starting User Profile synchronization:
Could not connect to http://spsrv:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it <ip-adress:port>. (read more...)
