Newbie: Using Caché for First Time

520 views
Skip to first unread message

ddspell-m3

unread,
Jun 3, 2008, 9:48:58 AM6/3/08
to intersystems.public.cache
My background: I've been a Pick programmer since 1987 when I started
with Prime INFORMATION. Since that time, I've used uniVerse and
currently, I'm using D3. Now I'm trying Caché.

I've downloaded and installed the software on Windows XP Pro. I
believe the database engine is running. I have a multivalue cube in my
system tray. I right click on it and select terminal. A blue window
appears and immediately, an error pops up.

The popup is titled "NTI Connection Error" and the message says:
cn_iptcp:127.0.0.1[23]
10061: [WINSOCK] host forcefully rejected connection request

Occurred in NTI::Connect()

I'm guessing that this may be a firewall issue, eh? However, I added
port 23 as an exception on my workstation. It appears to not have made
any difference.


Thanks,
Danny

David Shull

unread,
Jun 3, 2008, 12:17:48 PM6/3/08
to intersystems...@googlegroups.com

One thing to try would be go into the System Management Portal.  Select Security Management and then Services and make sure that the Telnet service is enabled.  Under Home-Configuration-Advanced Settings you should also see the Telnet Port configuration (default of 23).

-----Original Message-----
From: intersystems...@googlegroups.com [mailto:intersystems...@googlegroups.com] On Behalf Of ddspell-m3

Sent: Tuesday, June 03, 2008 8:49 AM
To: intersystems.public.cache
Subject: [Caché] Newbie: Using Caché for First Time

ddspell-m3

unread,
Jun 3, 2008, 12:27:40 PM6/3/08
to intersystems.public.cache
Thanks, I just tried it (http://127.0.0.1/csp/sys/UtilHome.csp), but
Internet Explorer cannot display the webpage.

Maybe something isn't installed correctly.

On Jun 3, 11:17 am, "David Shull" <davidksh...@hotmail.com> wrote:
> One thing to try would be go into the System Management Portal. Select
> Security Management and then Services and make sure that the Telnet service
> is enabled. Under Home-Configuration-Advanced Settings you should also see
> the Telnet Port configuration (default of 23).
>
> -----Original Message-----
> From: intersystems...@googlegroups.com
>
> [mailto:intersystems...@googlegroups.com] On Behalf Of ddspell-m3
> Sent: Tuesday, June 03, 2008 8:49 AM
> To: intersystems.public.cache
> Subject: [Caché] Newbie: Using Caché for First Time
>

Alexander Riemer

unread,
Jun 3, 2008, 12:48:14 PM6/3/08
to intersystems...@info2.kinich.com
Hi Danny,

I believe the telnet service is not activated.

Start the System Management Portal (SMP) and go to security
management/services and click on the Telnet service. Check the activate box.

I'm not sure if the points I've mentioned are named correctly. I've
translated them from my German Caché installation. But it should give you
the idea.

Regards
Alex

"ddspell-m3" <dds...@gmail.com> schrieb im Newsbeitrag
news:4acc652c-f898-46e0...@i76g2000hsf.googlegroups.com...

Alexander Riemer

unread,
Jun 3, 2008, 12:50:33 PM6/3/08
to intersystems...@info2.kinich.com
Click on the Caché cube/System Management Portal. This should start it with
the built in Apache server usually running on Port 57772.

The URL should look like this: http://localhost:8872/csp/sys/UtilHome.csp

Regards
Alex

"ddspell-m3" <dds...@gmail.com> schrieb im Newsbeitrag

news:2ccb3d19-69b7-4838...@e39g2000hsf.googlegroups.com...

Mali Neelakantan

unread,
Jun 4, 2008, 12:27:25 AM6/4/08
to intersystems...@googlegroups.com
Sometimes we get this problem, this problem is because of windows not able to connect using winsock layer due to corruption in Winsock DB.  There is a documented issue in Microsft support site. Good news is you can recover from this problem whenever it happens.
 
These are symptoms of truly winsock issue:
 
a. You are not able to connect to your local host (127.0.0.1), cache terminal throws up winsock issue
b. You could face the same problem when you try to access any configured local web site through IE (127.0.0.1). (note this doesnot indicate that there is a winsock issue)
 
Resolution:
 

To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed, type netsh winsock reset at the command prompt, and then press ENTER

 

Detailed technical material about how to recover from this issue is documented 

http://support.microsoft.com/kb/936211/)

Hope this helps!

regards
-Mali

ddspell-m3

unread,
Jun 4, 2008, 3:11:35 PM6/4/08
to intersystems.public.cache
Tried what you suggested, but that didn't work. I think I need to
start over.

On Jun 3, 11:27 pm, "Mali Neelakantan" <m.neelakan...@gmail.com>
wrote:
> Sometimes we get this problem, this problem is because of windows not able
> to connect using winsock layer due to corruption in Winsock DB. There is a
> documented issue in Microsft support site. Good news is you can recover from
> this problem whenever it happens.
>
> These are symptoms of truly winsock issue:
>
> a. You are not able to connect to your local host (127.0.0.1), cache
> terminal throws up winsock issue
> b. You could face the same problem when you try to access any configured
> local web site through IE (127.0.0.1). (note this doesnot indicate that
> there is a winsock issue)
>
> Resolution:
>
> To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed,
> type netsh winsock reset at the command prompt, and then press ENTER
>
> Detailed technical material about how to recover from this issue
> is documented
>
> http://support.microsoft.com/kb/936211/)
>
> Hope this helps!
> regards
> -Mali
>

ddspell-m3

unread,
Jun 5, 2008, 12:12:56 AM6/5/08
to intersystems.public.cache
Okay, I downloaded the latest version (offline) and installed it. It
said it installed successfully.

When it tried to take me to the Getting Started web page, I got an
HTTP 500 error. So now I'm thinking that the web server isn't running.
Isn't that supposed to start automatically as part of the install?

This is starting to get a little frustrating.

ddspell-m3

unread,
Jun 5, 2008, 9:25:32 AM6/5/08
to intersystems.public.cache
Okay, I'm pretty certain that I don't have a web server running.
However, according to the tutorial, Caché includes a light-weight,
built-in HTTP server. Although, it appears that isn't working.

So it looks like I don't have IIS installed/running, Apache installed/
running or Caché's web server running. So how do I remedy this?


Thanks,
Danny

On Jun 3, 11:27 pm, "Mali Neelakantan" <m.neelakan...@gmail.com>
wrote:
> Sometimes we get this problem, this problem is because of windows not able
> to connect using winsock layer due to corruption in Winsock DB. There is a
> documented issue in Microsft support site. Good news is you can recover from
> this problem whenever it happens.
>
> These are symptoms of truly winsock issue:
>
> a. You are not able to connect to your local host (127.0.0.1), cache
> terminal throws up winsock issue
> b. You could face the same problem when you try to access any configured
> local web site through IE (127.0.0.1). (note this doesnot indicate that
> there is a winsock issue)
>
> Resolution:
>
> To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed,
> type netsh winsock reset at the command prompt, and then press ENTER
>
> Detailed technical material about how to recover from this issue
> is documented
>
> http://support.microsoft.com/kb/936211/)
>
> Hope this helps!
> regards
> -Mali
>

ddspell-m3

unread,
Jun 5, 2008, 2:46:56 PM6/5/08
to intersystems.public.cache
Never mind. I got some help from InterSystems. They said it was
probably a security issue. Actually, I had tried this once before last
year and had abandoned it. This is my second time and instead of doing
a new install, I had tried to just upgrade what I had. Apparently,
that installation was a mess, so the solution was to do a new install.

I've gone through the MV tutorial and I'm happy with what I've seen so
far.

On Jun 3, 11:27 pm, "Mali Neelakantan" <m.neelakan...@gmail.com>
wrote:
> Sometimes we get this problem, this problem is because of windows not able
> to connect using winsock layer due to corruption in Winsock DB. There is a
> documented issue in Microsft support site. Good news is you can recover from
> this problem whenever it happens.
>
> These are symptoms of truly winsock issue:
>
> a. You are not able to connect to your local host (127.0.0.1), cache
> terminal throws up winsock issue
> b. You could face the same problem when you try to access any configured
> local web site through IE (127.0.0.1). (note this doesnot indicate that
> there is a winsock issue)
>
> Resolution:
>
> To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed,
> type netsh winsock reset at the command prompt, and then press ENTER
>
> Detailed technical material about how to recover from this issue
> is documented
>
> http://support.microsoft.com/kb/936211/)
>
> Hope this helps!
> regards
> -Mali
>

Jon Jensen

unread,
Jun 6, 2008, 8:00:33 AM6/6/08
to intersystems...@info2.kinich.com
I noticed in your thread you mention MV. I wanted to let you know about
an additional resource for your MV specific issues with Cache'(you may
already know, but just in case).

http://groups.google.com/group/InterSystems-MV/topics

hth
jon

ddspell-m3

unread,
Jun 6, 2008, 11:29:59 AM6/6/08
to intersystems.public.cache
Jon,


Thanks, I guess I posted to the wrong newsgroup.


Regards,
Danny

Jon Jensen

unread,
Jun 9, 2008, 7:01:55 AM6/9/08
to intersystems...@info2.kinich.com
I think your post here was appropriate - you wanted info about the
setup/config/etc.

I had just wanted to let you know about a group for MV specific issues
in Cache'(once you are up and running)

jon

Reply all
Reply to author
Forward
0 new messages