Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CMS Conflict

Status
Not open for further replies.

DPhil

Technical User
Sep 6, 2002
168
GB
Is there a known list anywhere of applications that conflict with CMS?

If anyone knows of any can they be posted here?

At present we are having problems with

Landesk and an Access database
 
What is the relation between Landesk, Access, and CMS? Applications never conflict: it is always interactions which might conflict. What interactions have you implemented?
 
We have Superviser 8 running on desktops/laptops with other applications e.g. Access databases and landesk amongst others. When logging in we get these errors from CMS since Landesk introduced and intermittantly before. I seem to remeber that Supervisor doesn't like certain databases running at the same time.

"The server did not recognize your Login ID and/or Password, your Login shell is not set to CMS, or (V* CMS only) cmsadm backup is running. Please try again or contact your system administrator."

" cvsSRV.exe. has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created"

"The operation could not be completed.
Error; -2147023174- Number of calls outflowed from direct agentqueue
Location: Main_DoAction"

Any pointers greatly excepted









 
Hi Phil,
Hope you recieved the stuff I sent you! We have Access running on win2k machines here that also use CentreVu 8.0. We have had problems but not really related to Access. We have a prob where the CentreVu interface crashes and disappears but the app is still running when you look at Task Manager. Our tech support are still scratching their heads.....
Also we get an issue where the agent gets a login error with just a number on and the way to cure that is to delete the local cache.tmp file in the Lucent directory on the machine. Other than that it goes okay. John
ski_69@hotmail.com
 
John

Got the stuff thanks.

We have removed the cache.tmp, standard Avaya response I believe!?
we are awaiting another patch from Avaya addressing the problem.

If we can build a list which may help in the future to preempt any conflicts and solutions that would be grate.

all machines are W2K

Dave

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top