<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Leslie,<br>
<br>
It is my understanding that the fix will require running instcat.sql on
the CM server to reconfigure SQL server instance on CM. In the article
this script appears to "upgrade the system stored procedures". This
sounds very dangerous for the CM server. I am not aware of any effort
by Cisco to certify this patch. Additionally development has stopped
on windows branch so additional testing appears very unlikely.<br>
<br>
The challenge, as i see it, is you need a sqk2k5 server to communicate
with the sql2k instance on cm. Accomplishing this requires "upgrading
system stored procedures" on the sql2k instance. While that may safe
for microsoft it is unclear what that may cause for the cisco
applications accessing the sql database.<br>
<br>
if you must do this please test on a lab scenario first.<br>
<br>
/Wes<br>
<br>
On Monday, July 06, 2009 11:13:30 AM, Leslie Meade
<a class="moz-txt-link-rfc2396E" href="mailto:lmeade@signal.ca"><lmeade@signal.ca></a> wrote:<br>
<blockquote
cite="mid:EAF4FF4AB2142D499F2F5A3B9D85152904BC8B24@exch-bo.MGVFS.McLeanNet"
type="cite">
<pre wrap="">I hear you loud and clear.
But I think I explained myself incorrectly.
The app is called Billback and it resides on another server and the sql
on that server fires a query off to the CDR table on the Callmanager.
Funny thing is I put the issue into TAC and the first level said it
should be fine, but he also said that he would check it out with the
developers first. So I am awaiting some more information from both
sides.
Leslie
-----Original Message-----
From: Wes Sisk [<a class="moz-txt-link-freetext" href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</a>]
Sent: Monday, July 06, 2009 7:41 AM
To: Leslie Meade
Cc: cisco-voip
Subject: Re: [cisco-voip] Billback software upgrade
I strongly recommend against this. Replacing any drivers on the CM
server itself is likely to cause issues. Your network so your choice.
TAC will not support this.
/Wes
On Thursday, July 02, 2009 1:41:00 PM, Leslie Meade <a class="moz-txt-link-rfc2396E" href="mailto:lmeade@signal.ca"><lmeade@signal.ca></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have a client that uses a Billback data base and they upgraded it
from sql 2000 to sql 2005.
Now they are getting sql errors like
OLE DB provider "SQLNCLI" for linked server "172.16.1.10" returned
message "Unspecified error".
OLE DB provider "SQLNCLI" for linked server "172.16.1.10" returned
message "The stored procedure required to complete this operation
could not be found on the server. Please contact your system
</pre>
</blockquote>
<pre wrap=""><!---->administrator.".
</pre>
<blockquote type="cite">
<pre wrap="">Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB
provider "SQLNCLI" for linked server "172.16.1.10". The provider
supports the interface, but returns a failure code when it is used.
Microsoft identifies the problem as the system stored procedures not
being upgraded when SQL 2000 was upgraded from SP3 to SP4.
The link for the fix is: <a class="moz-txt-link-freetext" href="http://support.microsoft.com/kb/906954">http://support.microsoft.com/kb/906954</a>
The fix is to run instcat.sql against the CCM instance of SQL 2000.
Does anyone know of an issue with this? I am very dubious about
anything SQL related to the call managers so I thought I'd ask here
before asking TAC
Leslie
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>