Thursday, August 20, 2009

Office Sharepoint Server search not appearing in services list

The issues pertains to search which was missing from the "services on server" display (via Central Admin -> Operations -> Services on Server). Also the server roles list was disabled.
As the search service isn't present, SSP will not be created as there are no indexers.
This issue comes up because of configuration issue. While installing MOSS 2007, if WFE option is selected and not Complete installation, this issue will come up. It is mandatory to select "Complete installation" rather than doing a "Web front End" installation.
We can confirm if the MOSS installation is a complete or WFE one by going to the PSC diagnostics logs present in "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS". Search for the entry "Setting server role to WFE". This shall confirm if the installation is a WFE one.

Hope this helps.

Friday, August 14, 2009

AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009 when exporting data from excel

When we are exporting data from excel sheet to a table in a SQL 2005/2008 database. we come across an error "the AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009". This error comes up when the run64bitruntime is in True State.
The state can be changed to false by following the below steps.
1> go to soution explorer. Right click on the SSIS project and then click on properties.
2> Then in the property box, select debugging in the left pane.
3> Then in the right pane, we can see Run64bitRuntime is set as True. Please change it False. This shall resolve the issue.

Monday, August 3, 2009

Connect to SQL EXPRESS remotely

There has always been issues connecting to SQLEXPRESS instance using the SQL Server Management Studio (SSMS).

Steps to connect to SQL EXPRESS from other machine SSMS.

1> Enable TCP/IP
a> Launch the SQL Server Configuration Manager from the "Microsoft SQL Server 2005 CTP" Program menu
b> Click on the "Protocols for SQLEXPRESS" node,
c> Right click on "TCP/IP" in the list of Protocols and choose, "Enable"

2> Go to Surface area configuration of SQL Server. Click on Surface Area Configuration for Services and Connections.Check that Services are running. Then click on remote connection and check if Local and remote connections are selected with using both TCP\IP and named pipes option selected.

3> Providing a Port Entry
a>Go to the TCP/IP in the Protocols for SQL Express section in the configuration Manager.
b> Right Click on TCP/IP and select Properties.
c> Then select the IP Addresses tab in the Property box. Then scroll down to a entry on the right panel for "IPAll".
d> Clean up the TCP Dynamic Port option and in the TCP Port option provide a port number for example, 2301.
e> Then click OK. Restart the SQL Services.

4> A way to check the connection is using SQLCMD from a remote machine and connect like this:
The "," in the server name tells SQCMD it's a port.

5> Enabling the Firewall
a> Click on Start --> Administrative tools --> Windows Firewall with advanced Security.
b> Then right click on Inbound Rules and select New Rule. Select Rule type as Port. Click on Next. Then in Protocol and Ports, Select TCP, in the specific local Port provide the port number 2301. Then click on Next.
c> Then select the default as present and then click on Next. In the End provide the Name and click on Finish.

Once this is done, Check the connection using the SSMS from a remote machine.