Archivo de Marzo de 2012
Access Services is one of new features available in SharePoint 2010, which makes it possible either creating Web Database Sites or publishing a Microsoft Access database as a SharePoint 2010 Site. Then, the client/user can access this Microsoft Access database from SharePoint without the need of having Microsoft Access installed (only the Internet Explorer browser is needed). However, after creating a Web Database site you could get the Failed to start macro VerifyUsers error message. What’s happening?
A typical error when installing the Service Pack 1 for SharePoint 2010 is the error message The installation of this package failed. Maybe a too generic error message to find out why the installation of Service Pack 1 for MOSS 2010 fails, but with a quick review we’ll find the usual reason for which this error occurs: Not enough disk space. Extend disk (or free up space), and the installation of Service Pack 1 for SharePoint 2010 will end with success.
In the last few days I have been working on a Windows Server 2008 R2 installation having Directory Services and DNS roles enabled. However, after installing Exchange Server 2010, I found out that the DNS Server service was stopped. Then I was looking for additional details and… the DNS Server service had never started on boot. It always got the following error message on the System Event Log: The network is not present or not started (Event ID 7023). However, I could start the DNS Server service manually (once Windows was started) without any problem. In addition, the Intersite Messaging service could not start on boot.
Sometimes, we found out that we cannot access as SysAdmin to an existing SQL Server or SQL Express instance, because we have not any user with elevated privileges on SQL Server, even though being member of the local Administrator group. In this scenario we can try to start the SQL Server instance on Single User mode and connect to it using a local administrator user, to take ownership, creating a user login configured as SysAdmin. This Workaround is quite helpful in Outsourcing projects, corporate mergers, SharePoint 2010 farms installed on StandAlone mode, and so on.
This week I got a The Workstation service has not been started error message when I was trying to create/add a new Content Database on a SharePoint Foundation 2010 StandAlone farm using the Central Administration. But the Workstation service was working successful. Looking for additional details, I found out that I couldn’t create a New Web Application because the New Web Application button was disabled on the SharePoint 2010 Central Administration. However, there is an easy solution for that issue.