7/8/2025 12:34:01 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the code of conduct for posting guidelines.
|
|
|
|
SLX goes unavailable!
Posted: 16 Jan 07 8:29 AM
|
fiogf49gjkf0d We have 2 slx production systems sitting in our prod server(Pretty good
configs and all those good h/w components and lotsa free space)
As to the question of external processes, we have Scribe, KS and a
decent amount of .net customs(both windows and web) which works well
with it.
Starting last week of Dec, we have many instances where our components
fail sporadically with different error messages, all poiting to the
fact that when they occur , they dont see our application server ,
Server host or some shares created in our server(like the one below).
We have ppl coming in over the WAN and when they complain, we try to
log in as them in the home office and no problem!This is entirely not a
WAN issue as our .net components reside on the same server/another
server in the same domain.Transferring this issue to our network dept
is of no use as they are asking us to re-create the issue.
One of the Errors is ....
DirWatchThread.Execute Error: GetOverlappedResult call failed The
handle is invalid Directory: \\CrmXX01\slxprod sync logs\Documents
|
|
|
|
Re: SLX goes unavailable!
Posted: 16 Jan 07 10:07 AM
|
fiogf49gjkf0d Can't say I've ever seen that error (ever). Even googling doesn't uncover anything about that error.
Question though, are the logging directories (on CrmXX01) on the same server as the SLX server, or somewhere else? |
|
|
|
Re: SLX goes unavailable!
Posted: 16 Jan 07 1:43 PM
|
fiogf49gjkf0d I've gotten the same error message. Sync server resides on the same box as the host. Windows 2003 Standard server OS. In November and October, I got a thrashing of:
DirWatchThread.Execute Error: GetOverlappedResult call failed The handle is invalid Directory: \\(SERVER)\SyncLogs\Library.
and
DirWatchThread.Execute Error: ReadDirectoryChanges call failed. The handle is invalid Directory: \\(SERVER)\SyncLogs\Library.
It loops through more than just this directory (but they're all SLX shares: SpeedSearch, Attachments, the Library) and gave me a good number of messages (hundreds) all within the same block of time. One thing that is weird is SyncLogs are not located in Program Files like the speedsearch share is, though they are on the same drive. The system uptime shows the server didn't reboot and hasn't in a while but that also means it could use some updates from MS.
One thing I've noticed when doing dev work in VMWare is that when the network cable drops, the SLX link to \\Computer\ stops working. There's no indication in the eventlogs that the NIC lost connectivity due to a power outage or similar phenomenon but I don't believe our switches are on UPS backup so it may not have been down long enough to register a drop.
The problem hasn't come up since and it's apparently very sporatic. It hasn't happened any time before October that I recall, but my logs don't go back much further. I wish I had a way of generating the error 100% of the time because maybe then I could figure out exactly what causes it. |
|
|
|
Re: SLX goes unavailable!
Posted: 18 Jan 07 8:54 AM
|
fiogf49gjkf0d Exactly! your the first person who understand the nature of my problem and my pain at the same time...This is so sporadic and every dept in my company says this is not their problem because it is reported by either slx component / or my component or an MQ client or one of my aspnet pages or KS .
At this point except for the slxweb/aspnet piece , i have all components in one server which we will shortly be moving some of them to another server. |
|
|
|
Re: SLX goes unavailable!
Posted: 18 Jan 07 3:14 PM
|
fiogf49gjkf0d I have no components reporting errors, I just have an Event Log with over a hundred entries that take place within the matter of a 3 minute timespan. I have no idea what caused it because there isn't anything remotely close. Nothing rebooted, no service disconnected, nothing is a red flag.
You on the other hand seem to be in a better place. You have components reporting errors and I'm willing to bet your component logs could match error logs exactly. If this is true, it stands to reason that there may be a way to force it into this behavior. I'd be tempted to setup a perfmon to see if memory is being exhausted or a possible hardware issue is the cause but this happened on one day in November and one day in October, with 60+ some odd days in between of operating normally. If it were more frequent or users were reporting serious problems during that timeframe (it all happened during office hours) then I'd be more inclined to try whatever I could to look into it.
I'm actually surprised Ryan knows nothing of it because he has access to the BP newsgroups and I would have thought at least one of them or SLX themselves could shed some light on it. I don't even know the SLXDirectoryWatch's exact purpose, I just know it errors every now and again usually because of a filename issue but in rare ocassions, major errors cropped up. |
|
|
|
Re: SLX goes unavailable!
Posted: 19 Jan 07 7:49 AM
|
fiogf49gjkf0d Jeremy , Thanks for the reply...
My Non-SLX componenets also behave Ok most of the time it runs, except for some weird errors some time like my application server is not available , OR SLX client showing up an error like "Operation is not allowed when the connection is closed" OR "connection cannot be used to perform this operation"
MY MQ client would say it is a return code is XXXX - which means environment error.
Speedsearch would return an error saying "invalid handle: \\crmsrv01\speedsearch" is not accessible which it is....
.net win app would throw an error : Could not establish connection with SLXServer.
Check server is running and PORT is correct.
slx website would say the samething too..
When Errors are reported , we go and check and there is no problem for anything.Contact our network and they say everything is OK and there is no problem! All of this started happening the last week of Dec and everything was OK till then!
I am stumped!
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|