The Baretta

We were getting an issue on one of our Test Server WFE's where we were having two issues: - If you were trying to load an InfoPath form that contained a connection to the GetUserProfileByName Web Service, it would fail. - If you tried to connect to the site via SharePoint Designer, it would error out. SO!  If you get any of the following issues: In SP Designer: "The server could not complete your request.  For more specific information, click the Details button." "An error occurred while trying to fetch data from your SharePoint site.  Unexpected response from the server.  The content type of the response is "", The status code is "OK"." On an InfoPath Form: "There has been an error while processing the form.  An error occurred while trying to connect to a Web service" In SharePoint Logs: "The following query failed: GetUserProfileByName (User: xx\username, Form Name: Template, IP: , Connection Target:...

Just a quick one after some deep thought. Thoughts on the Future: If you have to create an InfoPath Form, you should be creating it as a List Form (if possible), not a Form Library.  The reason for this is ease of upgrade now that InfoPath will not be upgraded/supported by Microsoft. If you have to create a Form Library (because you form requires repeating tables/sections): I’ve decided that InfoPath forms should NOT be published as Content Types.  The only time it would be considered OK is if the form is very generic and is being used on multiple sites.  E.g. a Help Form which could be used by multiple departments without any modification. The main issue when publishing as a Content Type is that every field you promote to be visible in SharePoint has to be created as a Site Column. This means that even for a small form, for instance, a Personnel Access Form, you’d have to create Site Columns for fields like: Room Number or Access Hours, which would only ever be ...

Today I tried to log into our DocAve 6 Suite on our SharePoint 2010 environment and came across this error message: Sorry, the account has been disabled. Please contact the administrator My guess was that due to inactivity (hadn't logged in for a few months) the accounts had been disabled.  The problem was that every Administrator account had been disabled so I couldn't get in! After a quick call to AvePoint, the techies solved the issue quick smart.  Here's how you can save yourself a call and Enable a user accounts status again: Log onto the SQL Server that stores the AvePoint Databases. Navigate to AvePoint's ControlDB Right-Click >  Select TOP 1000 rows for the table dbo.AccountMapping In the results, you should see all your accounts, and a Status column which states whether the account is disabled or not (1 = disabled, 0 = enabled) Right click the dbo.AccountMapping table and Edit TOP 200 Rows , and modify the Status from 1 to 0 for the account in q...