Hi,

I get above error with details as "Server ODBC error.
Contact the site administrator." It happens
intermittently.Any idea how to resolve this ?

Thanks,
Pradnya

[ Post a follow-up to this message ]

Looks Like CMS cannot contact the SQL server intermittently . Is your DB on
a separate machine ?

Piyush

"Pradnya" <pradnya@singtel.com> wrote in message
 news:17c6401c421ff$8ddb8ed0$a001280a@phx
.gbl...
> Hi,
>
> I get above error with details as "Server ODBC error.
> Contact the site administrator." It happens
> intermittently.Any idea how to resolve this ?
>
> Thanks,
> Pradnya

[ Post a follow-up to this message ]

Yup, SQL database is on a separate server.Any
resolution/workaround to this problem ?

Cheers,
Pradnya

>-----Original Message-----
>Looks Like CMS cannot contact the SQL server
intermittently . Is your DB on
>a separate machine ?
>
>Piyush
>
>"Pradnya" <pradnya@singtel.com> wrote in message
> news:17c6401c421ff$8ddb8ed0$a001280a@phx
.gbl... 
>
>
>.
>

[ Post a follow-up to this message ]

Hi Pradnya,

Piyush is right.
Seems as if you have database connectivity issues.
MCMS uses the ODBC interface to connect to the database and relies on a
valid ODBC database connection.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Manasvin@msnews.microsoft.com" <manasvin@hotmail.com> wrote in message
news:OnRwndkIEHA.2972@TK2MSFTNGP12.phx.gbl...
> Looks Like CMS cannot contact the SQL server intermittently . Is your DB
on
> a separate machine ?
>
> Piyush
>
> "Pradnya" <pradnya@singtel.com> wrote in message
>  news:17c6401c421ff$8ddb8ed0$a001280a@phx
.gbl... 
>
>

[ Post a follow-up to this message ]

Hey Pradnya,

You may have to re-write the code to stop it from creating
too many CmsContexts within a single function call. Step
through the code and look for functions that create the
CmsContext and functions within the function that does
that. I've found that the problem is more pronounced when
using same variable names to hold the context within the
same HTTP request. I would suggest passing the context in
as a parameter insted of recreating it and disposing them
when you don't need it anymore.

I'm not convinced that it's a connection to the DB (seeing
that none of the other apps on the same server and web
site have this problem), it may be something to do with
the way the objects work (in particular, CmsContext) with
the database on the application level - just a pure guess.

Cheers to you too,
M

>-----Original Message-----
>Yup, SQL database is on a separate server.Any
>resolution/workaround to this problem ?
>
>Cheers,
>Pradnya
> 
>intermittently . Is your DB on 
>.
>

[ Post a follow-up to this message ]

Hi Pradnya,

you need to fix your database connection.
Ensure that the database is always available.
For details: post to a networking related newsgroup.
This is not a CMS topic.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Pradnya" <pradnya@singtel.com> wrote in message
 news:1cb2f01c42290$a5fcce20$a301280a@phx
.gbl...[vbcol=seagreen]
> Yup, SQL database is on a separate server.Any
> resolution/workaround to this problem ?
>
> Cheers,
> Pradnya
> 
> intermittently . Is your DB on 

[ Post a follow-up to this message ]

Hi Stefan,

I work with Pradnya.

The database is always available. Other modules are
connected to it and they don't get this problem. We are on
HA where the server is monitored. So if the database is
down, alarm bells start ringing and we will know. The
problem can be isolated to this particular module (whose
code I am partly responsible for and therefore know
it's "problems").

Curious, what kinds of connection issues do you suspect?

regards
M

>-----Original Message-----
>Hi Pradnya,
>
>you need to fix your database connection.
>Ensure that the database is always available.
>For details: post to a networking related newsgroup.
>This is not a CMS topic.
>
>Cheers,
>Stefan.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"Pradnya" <pradnya@singtel.com> wrote in message
> news:1cb2f01c42290$a5fcce20$a301280a@phx
.gbl... 
>
>
>.
>

[ Post a follow-up to this message ]

Hi M,

I'm not a networking expert. I only can say that this error message is
coming up from the ODBC layer - a part of the OS (MDAC) which reports a
problem with the database connection.
In the part I have seen this when (e.g.) a network card or a switch caused
troubles.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"M" <anonymous@discussions.microsoft.com> wrote in message
 news:1cc1001c422b1$a887e2d0$a501280a@phx
.gbl...[vbcol=seagreen]
> Hi Stefan,
>
> I work with Pradnya.
>
> The database is always available. Other modules are
> connected to it and they don't get this problem. We are on
> HA where the server is monitored. So if the database is
> down, alarm bells start ringing and we will know. The
> problem can be isolated to this particular module (whose
> code I am partly responsible for and therefore know
> it's "problems").
>
> Curious, what kinds of connection issues do you suspect?
>
> regards
> M
> 
> confers no rights. 

[ Post a follow-up to this message ]

Hi Stefan,

Is there a possibility that codes such as this could cause
this problem?

public void A()
{
CmsApplicationContext cmsContext = new
CmsApplicationContext()

//do whetever it takes to create new context

foreach(object in objectCollection)
{
call function B
}
}

public void B()
{
CmsApplicationContext cmsContext = new
CmsApplicationContext()
...

call B recursively
}

In essence, the CmsApplicationContext is created
repeatedly multiple times within a single request. Up to a
certain number (especially if they are all referenced by
local variables of the same name), the connection to the
DB starts to fail. There may be other factors, I'm not
sure. Wild guess: Is something getting pooled and maybe a
boundary condition breached?

I'm making a pure guess by linking the ODBC and the
CmsContext objects with this error. The reason behind this
is because when I cleaned up the codes to use a single
context within the functions, the problem disappeared.

It's only this *one* module (was rushed out hence the less
than perfect code). Other modules do not face this problem
and are executing fine, connecting to the database 100% of
the time, so I'm not leaning towards the network
connectivity side of the explanation ;-)

M

>-----Original Message-----
>Hi M,
>
>I'm not a networking expert. I only can say that this
error message is
>coming up from the ODBC layer - a part of the OS (MDAC)
which reports a
>problem with the database connection.
>In the part I have seen this when (e.g.) a network card
or a switch caused
>troubles.
>
>Cheers,
>Stefan.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"M" <anonymous@discussions.microsoft.com> wrote in message
> news:1cc1001c422b1$a887e2d0$a501280a@phx
.gbl... 
on[vbcol=seagreen] 
and[vbcol=seagreen] 
error.[vbcol=seagreen] 
>
>
>.
>

[ Post a follow-up to this message ]

Hi

Is it possible for you to monitor the number of connections and the like
using performance monitor on the CMS server machine ? This might give some
clues

Manasvin

"M" <anonymous@discussions.microsoft.com> wrote in message
 news:184db01c422c0$919b0f20$a001280a@phx
.gbl...[vbcol=seagreen]
> Hi Stefan,
>
> Is there a possibility that codes such as this could cause
> this problem?
>
> public void A()
> {
>   CmsApplicationContext cmsContext = new
> CmsApplicationContext()
>
>  //do whetever it takes to create new context
>
>  foreach(object in objectCollection)
>  {
>     call function B
>  }
> }
>
> public void B()
> {
>     CmsApplicationContext cmsContext = new
> CmsApplicationContext()
> ...
>
>   call B recursively
> }
>
> In essence, the CmsApplicationContext is created
> repeatedly multiple times within a single request. Up to a
> certain number (especially if they are all referenced by
> local variables of the same name), the connection to the
> DB starts to fail. There may be other factors, I'm not
> sure. Wild guess: Is something getting pooled and maybe a
> boundary condition breached?
>
> I'm making a pure guess by linking the ODBC and the
> CmsContext objects with this error. The reason behind this
> is because when I cleaned up the codes to use a single
> context within the functions, the problem disappeared.
>
> It's only this *one* module (was rushed out hence the less
> than perfect code). Other modules do not face this problem
> and are executing fine, connecting to the database 100% of
> the time, so I'm not leaning towards the network
> connectivity side of the explanation ;-)
>
> M
> 
> error message is 
> which reports a 
> or a switch caused 
> confers no rights. 
> on 
> and 
> error. 

[ Post a follow-up to this message ]