The Temple of Fu

code, systems and games

Archive for April 2010

Change Desktop Environment – xwmconfig

leave a comment »

I am not going to get into what is a Desktop Environment or Window Manager you can read what they are here, suffice it to say the tool xwmconfig allows you to select either. It is ran like so.

%xwmconfig

From the list that is given to you select the Desktop Environment or Window Manager you want to use and there you go (personal preference is Fluxbox)! If you run the above command as root it will be a system wide setting.

Extra: Here is a great write up on Fluxbox configuration files.

Slack or Die!!!

Resources:
http://www.slackbook.org/

Written by lordfu

April 23, 2010 at 3:07 pm

Posted in Linux, Slackware

Server is not configured for RPC(Remote Procedure Calls)

with 4 comments

I was setting up a new database on a new SQL Server 2005 installation that has a few linked servers configured (which happen to be SQL Server 2000), while testing execution of a remote stored procedure it failed with the error:

Msg 7411, Level 16, State 1, Line 1
Server 'psp6new' is not configured for RPC.

The problem was that RPC was not configured for the linked server. this is not set by default, you can see what settings are configured with
exec sp_helpserver

If ‘rpc and rpc out’ are not in the results, then the the linked server isn’t configured for RPC. To do so:

exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'
exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'

Or alternatively you can right click on your linked server bring up it’s properties and select True for the value from the RPC and RPC Out rows.

Set True for values RPC and RPC Out

Hope this helps!

Written by lordfu

April 23, 2010 at 10:51 am

Posted in Database, Development, MSSQL

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 – No connection could be made because the target machine actively refused it.)

leave a comment »

Ok I am not a SQL god and make no claims of even being a SQL guru so this will be short and sweet.

I received this error on a new SQL Server 2000 install (hey some have legacy systems to support still!) while trying to connect from a web application.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 – No connection could be made because the target machine actively refused it.)

After a day or so of trouble shooting and testing different configurations, the standard tests Named Instance vs TCP/IP, firewalls, user name password, connection strings, tel-netting etc, it boiled down to SQL server SP4 not being installed on the SQL server. After we installed SP4 all was good.

Hope this helps someone!

Written by lordfu

April 16, 2010 at 3:34 pm