Russ' Do It Yourself Home Workshop

Finding Fixes to Just About Anything and Everything

Archive for April, 2014

Dropped Connections on SAP and the KeepAlive (rdisp/keepalive) Parameter

Posted by Russell Wright on April 28, 2014

We were experiencing issues with our SAP GUI connections dropping somewhat randomly, but more so when connected wirelessly or through VPN to our SonicWALL TZ 200.  This is probably a result of the SonicWALL aggressively closing connections and therefore causing SAP to drop the connection to the client.  In the SM21 log, a dropped connection entry looks like this.

image

There are several parameters in SAP that deal with connections, but we’re not talking about wanting to forcibly log off clients from our demo/test system.  What we want is to keep the connection to SAP alive as long as possible.  SAP OSS note 27320 provides a better definition of a couple of the parameters in question.  The definitions are repeated here for convenience.

rdisp/keepalive
——————–
Parameter for application servers, unit seconds, default 1200.
If the frontend has not sent any data to the application server for "keepalive" seconds, the
application server sends a short "Ping" message to the frontend. The frontend should answer within
the next 40 seconds with "Pong", otherwise the application server assumes that the link is dead and
releases all resources to the corresponding user. An error line "DP_CONN_DEAD" then appears in the
trace file dev_disp.
This usually occurs when a user switches off their PC without carrying out the shutdown procedure.
A value of 0 means that no check occurs.

rdisp/gui_auto_logout
————————-
Parameter for application servers, unit seconds, default 0.
If the frontend has not sent any data to the application server for "gui_auto_logout" seconds, the
frontend closes the user connection and releases the resources.
A value of 0 means that no users are logged off automatically.

One way to carry out this change, use the RZ10 transaction.

image

Select the appropriate Instance profile.

image

Select Extended maintenance and the Change button.

image

Select the Parameter button to add a new parameter.

 

image

Enter the rdisp/keepalive parameter and a number of seconds.  I’ve entered 180 seconds (3 minutes) in this case.  Press Enter to validate.

image

Select Copy.

image

You should see the parameter entered.

image

When you back out of the transaction, it will ask you to save your changes.

image

You should see a validation that the changes were accepted.

image

Now check your work by selecting the profile and selecting Display.

image

You should see the rdisp/keepalive parameter.

image

You now need to recycle your SAP instance for the parameter to be enforced.

image

Advertisements

Posted in Computer Software, SAP | Leave a Comment »

Getting SQL Express to Listen So You Can Connect Remotely

Posted by Russell Wright on April 22, 2014

Dang!  We had a situation where a new tool we were implementing in our back office, BillQuick Web Services 2014, would not use SQL Server since we purchased the "Pro" version and not the "Enterprise" version.  Unfortunately, it appears the trial version we installed has all the enterprise version capabilities and, after entering our license information, we were locked down to the pro version and it wouldn’t connect to the SQL Server anymore.

So, that meant I needed to install SQL Express to support the tool.  Okay, no biggie…except for the fact that SQL Express does not enabled Named Pipes or TCP/IP protocols, by default.  This took me a bit to figure out.

This is not a new problem, as posted by Peter van Ooijen in 2006.  Some things never change…

The easy way to fix this is to use SQL Server Configuration Manager.

image

Navigate to the Protocols section for your SQL Express instance and switch it on! 

image

And if that’s not enough, you need to change the TCP/IP properties to listen on the correct port.  I set the port to 1077 (one the SQL Server is NOT listening on).  It appears if you set it in the the IPAll section, the same port will be used for each IP address and you only have to enter it one time.

image

Oh, and then recycle your SQL server instance!

The connection string to use looks like this.

SQLServer\Instance,Port

image

 

Posted in Computer Software, SQL Server | Leave a Comment »

First Alert 9120B Smoke Detector Keeps Chirping/Beeping

Posted by Russell Wright on April 4, 2014

I had a smoke detector that kept chirping.  Thinking it was a battery problem, I replaced the battery even though the battery that was in it tested out okay.  Now, this is a smoke detector located at the top of the stairs, so I had to get my folding ladder out to get to it.  You know…two ladder feet on a stair and the other two feet of the ladder on the top of the stair landing with 6′-1", 210 lb. me standing on the ladder, reaching for the ceiling.  Not a pretty sight.  And, to make matters worse, the dang thing kept on beeping after I replaced the battery.

image

So, standing on the ladder (I didn’t put it away because I thought this might happen), I removed the smoke detector by rotating it CCW to detach it from its base so I could get to the plug on the back.  After unplugging it (and not falling off the ladder) I took it downstairs and removed the cover.  There are three plastic tabs/clips that can be released, one-at-a-time, to allow you to remove the cover.  I took the naked smoke detector out to the garage and fired up the air compressor (what…you don’t have one?) and blew the sensor clean.  I reassembled the detector (snapped it together) and put the original battery back in it and voila, no more chirping!

This detector is located near our attic fan, so I’m thinking it gets a lot of dust and particulate matter blown by it when the fan runs.  However, it looked very clean on the inside, but blowing it out appears to have done the trick.

Posted in Home Repair, Misc Repair | 3 Comments »