dbTalk Databases Forums  

D3_RPC Errors shut down the VME

comp.databases.pick comp.databases.pick


Discuss D3_RPC Errors shut down the VME in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Peter
 
Posts: n/a

Default D3_RPC Errors shut down the VME - 07-11-2005 , 11:06 PM






Hi,
After upgrade from D3NT 7.3.4 to 7.4.4 we are constantly getting D3_RPC
errors and eventually it shuts down the server without warning. This
happens at least once a day. We've recently upgraded to 7.4.5 but the
problems are the same.
RD support doesn't know what the problem is.....
These problems are the same on Win 2000 server and Win XP server, so my
guess is that it must be D3.
Has anyone had this sort of problems with it? Do you have any
solutions?
Do you think it would be a good idea to change it back to 7.3.4?

Thank you


Reply With Quote
  #2  
Old   
Mark Brown
 
Posts: n/a

Default Re: D3_RPC Errors shut down the VME - 07-11-2005 , 11:57 PM






What does the Event Viewer show as a typical error?

Are they "application" or "system" errors?

Mark Brown


"Peter" <peter (AT) ramto (DOT) com> wrote

Quote:
Hi,
After upgrade from D3NT 7.3.4 to 7.4.4 we are constantly getting D3_RPC
errors and eventually it shuts down the server without warning. This
happens at least once a day. We've recently upgraded to 7.4.5 but the
problems are the same.
RD support doesn't know what the problem is.....
These problems are the same on Win 2000 server and Win XP server, so my
guess is that it must be D3.
Has anyone had this sort of problems with it? Do you have any
solutions?
Do you think it would be a good idea to change it back to 7.3.4?

Thank you




Reply With Quote
  #3  
Old   
Peter
 
Posts: n/a

Default Re: D3_RPC Errors shut down the VME - 07-12-2005 , 12:38 AM



It is application error log.
Usually D3_RPC ... Cannot get a valid binding handle

Peter


Reply With Quote
  #4  
Old   
Mark Brown
 
Posts: n/a

Default Re: D3_RPC Errors shut down the VME - 07-12-2005 , 10:05 AM



That usually means the system name has changed and now D3 can't find itself.

I feel like that a lot.

Mark Brown


"Peter" <peter (AT) ramto (DOT) com> wrote

Quote:
It is application error log.
Usually D3_RPC ... Cannot get a valid binding handle

Peter




Reply With Quote
  #5  
Old   
Peter
 
Posts: n/a

Default Re: D3_RPC Errors shut down the VME - 07-12-2005 , 04:41 PM



Thanks Mark,
this is a new installation so the name hasn't changed.


Reply With Quote
  #6  
Old   
Frank Winans
 
Posts: n/a

Default Re: D3_RPC Errors shut down the VME - 07-13-2005 , 12:03 PM




"Peter" wrote
After upgrade from D3NT 7.3.4 to 7.4.4 we get application
log errors "D3_RPC ... Cannot get a valid binding handle"

"Mark Brown" wrote
That usually means the system name has changed and now D3 can't find itself

"Peter" wrote
Quote:
Thanks Mark, this is a new installation so the name hasn't changed.
Mark's probably right, the 'mds server name' doesn't resolve [seen through
microsoft's SMB networking subsystem] to this box's tcp/ip address;
testing for this is easy;
1) go into the d3/nt config windows and note down the mds server name
you've declared, for example mybox. Should match this computer's
windows networking id
2) open a command prompt window and run commands to test that this
box considers itself to be of that name

ping mybox

net view mybox
{shows list of printer/disk shares, or says so if there are none.
doing net view bozo
where there is no such computer bozo will pause and then gripe}





Reply With Quote
  #7  
Old   
Peter
 
Posts: n/a

Default Re: D3_RPC Errors shut down the VME - 07-14-2005 , 03:25 AM



Frank,
all these settings have been checked and they are ok.
We had RD support looking into this and they couldn't find anything.



Frank Winans wrote:
Quote:
"Peter" wrote
After upgrade from D3NT 7.3.4 to 7.4.4 we get application
log errors "D3_RPC ... Cannot get a valid binding handle"

"Mark Brown" wrote
That usually means the system name has changed and now D3 can't find itself

"Peter" wrote
Thanks Mark, this is a new installation so the name hasn't changed.

Mark's probably right, the 'mds server name' doesn't resolve [seen through
microsoft's SMB networking subsystem] to this box's tcp/ip address;
testing for this is easy;
1) go into the d3/nt config windows and note down the mds server name
you've declared, for example mybox. Should match this computer's
windows networking id
2) open a command prompt window and run commands to test that this
box considers itself to be of that name

ping mybox

net view mybox
{shows list of printer/disk shares, or says so if there are none.
doing net view bozo
where there is no such computer bozo will pause and then gripe}


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.