Wednesday, March 28, 2012
More MSDE Installation Problems.
mples refer to the PUBS database which I can't find anywhere. Did it not come wrapped up in MSDE?
I have W2K Pro, Visual Studio .NET 2003, MSDE loaded v8.00.760. Is there anybody out there that can help a .NET newbie out. The guy the company had hired to come in here and start our .NET efforts has quit and dumped all this in my lap. I am familiar with
Visual Studio 6; however, we hav always used Sybase Anywhere before. Any help will be appreciated.
Kenneth A. Jinks, Jr.
Lead Project Software Engineer
LabCorp CPG - LCM Development
Huntsville, AL
> examples refer to the PUBS database which I can't find anywhere.
http://www.microsoft.com/sql/downloads/default.asp#code
http://tinyurl.com/2oyvh
Maybe you didn't permit network access, set a sa-password, didn't disable
antivirus or anything like that?
Regards,
Lars-Inge Tnnessen
www.larsinge.com
Monday, March 26, 2012
More details for: SSPI context / [DBNETLIB][ConnectionRead (recv()).] General network error
since over a week I've been looking to
find out the reason for two error messages I get from our users and
servers, unfortunately without success up to now.
I really hope you can help me.
We are using Win 2k servers with active directory and SQL Server 2000,
clients are all Win XP with SP2. Versions of access are 2002 &
2003. The errors are userspecific and occur in both versions. The
SQL-Servers are accessed with an adp-file in 2002-format.
We have one usergroup which is member of specially many groups. This
affects the size of their windows access token which becomes constantly
larger. In order to enable those users to still access their mailboxes
on our Exchange servers, the DWORD entry "MaxTokenSize" with the
decimal value "65535" was made to the newly created key "Parameters" of
their registry branch
"HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos ".
Since then those users can not access any of our SQL Servers using the
windows authentification. One of them gets the error
"[DBNETLIB][ConnectionRead(recv().] General network error. Check your
network documentation.", the others the error "Check connection:
Failed: Cannot generate SSPI context".
In case of resetting the registry entries (by deleting them), the one
user receives the same error message as the rest while it doesn't make
any difference to those (but at least they can't connect to their
mailboxes).
After having researched the web, I realised in one of the SQL-Servers
logfiles the entry "Invalid buffer received from client.." which lead
me to start to believe it could have to do something with the kerberos
encryption in the first place. Therefore I asked if changes to the
tokensize had been made. I applied the change with "EXEC sp_configure
'network packet size', 65535 RECONFIGURE" on our testsystem and "EXEC
sp_configure" confirms that the value is run.
Consequence: The entry in the SQL Server log doesn't appear any longer, but the users still receive their error messages.
Do you have any hints?
Your comments will be highly appreciated!
Regards,
caracol
Hi, CaraCol
Your case seems interesting. The error you hit is very general and could has various causes. So, please first check following blogs to see whether they resolved your problem:
http://blogs.msdn.com/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/15/481297.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx
http://blogs.msdn.com/sql_protocols/archive/2007/01/02/cannot-generate-sspi-context-error-message-poisoned-dns.aspx
If they not, can you provide more detail answer about your system configuration by fllowing up the guideline:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1
Thanks!
Ming
|||Hi Ming,thanks for your informationsites. I had already tried out parts of it but reviewed them all the same.
The SPN does work correctly, otherwise our other usersgroups wouldn't be able to connect to our servers. I double checked this by setspn -l domain\accountname and got the desired result on the rigth port.
When turning on Named Pipes and restarting the instance on the serverside while activating NP on the clientside only (cliconfig.exe), we get the error message "Error on testing the connection while initialising the provider. [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied" (My error messages are translated from our german clients).
We are running SQL Servers 2000 Standard English Edition (8.00.760 SP3) on English W2k servers with SP4 and we use named instances with TCP/IP only.
Our clients are WinXP Pro with SP2 and Access 2002 (MDAC 2.70.7713.0) or Access 2003 (MDAC 2.81.1117.0). Connection is made by Access.
Aliases are not existent.
The service account is a domain administrator.
Service of WinXP SP2 Firewall is deaktivated or the firewall is configured as inactive.
There is no encryption enforcement.
Users are local admins.
We have installed Trend Micro Server Protect / Antivir Corporate Edition 5.58 respectively on every machine. A firewall is not provided by this version.
The Clients are shut down every day, so I doubt deleting the cached credentials when they should be deleted after every restart would make any difference.
Do you have any ohter hints?
Thanks again.
Regards,
caracol|||
Hi, Caracol
Sorry, I am confused the error you came across, is it "Can not generate SSPI Context" or " General Network Error"? If it is the latter, [DBNETLIB][ConnectionRead (recv()) indicates connection failed during your DB operation, so, please try
1) http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx
2) Open SQL Server Profile, repro the issue, see which specific client operation caused the failure, also, check server ERRORLOG or EventLog to find clue.
3) What if you enable NP on the SQL Server, and make np connection from client, see whether same issue occured? Or at least whether the "SSPI Context" error persist?, If so, that might due to your domain configuration issue.
BTW, It'd better upgrade your SQL Server 2000 from SP3 to SP4, this might be a known issue in SP3 but fixed in SP4 or SQL 2005.
Good Luck!
Ming.
|||http://support.microsoft.com/kb/814401
http://www.sqlservercentral.com/columnists/cmiller/cannotgeneratesspicontext.asp
|||Hi Satya,thanks for your interest, but your links are just some of the standard ones I came over a dozen times.
Regards,
caracol|||Hi Ming,
thanks again for your enthusiasm.
As I described, I got different messages depending on the configuration.
TCP/IP:
Quote:
"Since then those users can not access any of our SQL Servers using the windows authentification. One of them gets the error "[DBNETLIB][ConnectionRead(recv().] General network error. Check your network documentation.", the others the error "Check connection: Failed: Cannot generate SSPI context"."
-> This ist the configuration I started with and where the error occured the first time.
NP:
Quote:
"When turning on Named Pipes and restarting the instance on the serverside while activating NP on the clientside only (cliconfig.exe), we get the error message "Error on testing the connection while initialising the provider. [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied" (My error messages are translated from our german clients)."
-> This is what I tried later on to see if changing access method might succeed.
I have no idea, why this specific user on TCP/IP gets the error "[DBNETLIB][ConnectionRead(recv().]" while the rest gets
"Check connection: Failed: Cannot generate SSPI context". It must have to do with the profile, though, as it doesn't matter on which client he's logged on.
Quote from your last answer:
{1) http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx }
-> I already got over this due to your post from 01-02-2007, it was one of the sublinks over there. Therefore, this info was not helpful this time.
{2) Open SQL Server Profile, repro the issue, see which specific client operation caused the failure, also, check server ERRORLOG or EventLog to find clue.}
-> Standard to revise the logs again, so not helpful. I described that the users can't even log in to SQL server any longer, and that access 2002 / 2003 is this client. It is nothing else than access' standard connection that doesn't work, nothing of specific client operation.
{3) What if you enable NP on the SQL Server, and make np connection from client, see whether same issue occured? Or at least whether the "SSPI Context" error persist?, If so, that might due to your domain configuration issue.}
-> I wrote that I already had tried out NP, again Quote:
"When turning on Named Pipes and restarting the instance on the serverside while activating NP on the clientside only (cliconfig.exe), we get the error message "Error on testing the connection while initialising the provider. [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied" (My error messages are translated from our german clients)." So, not helpful, as I already decribed which error the users get in this case.
{BTW, It'd better upgrade your SQL Server 2000 from SP3 to SP4, this might be a known issue in SP3 but fixed in SP4 or SQL 2005.}
-> Finally another idea, thanks. As we have one version on every server worldwide, I'm in no possition to just install SP4 on one or a few of them, but I'll make the proposition to upgrade worldwide to SP4. We'll at least try this out in our test environment and see if it is of any help, although {"this might be a known issue in SP3 but fixed in SP4 or SQL 2005"} is not what commercial operations consider to be trustworthy or even professional. (This is meant as hint for MS, not to you personally.)
Nevertheless, I thank you very much for taking your time again to try to assist me.
Regards,
caracol
More details for: SSPI context / [DBNETLIB][ConnectionRead (recv()).] General network error
since over a week I've been looking to
find out the reason for two error messages I get from our users and
servers, unfortunately without success up to now.
I really hope you can help me.
We are using Win 2k servers with active directory and SQL Server 2000,
clients are all Win XP with SP2. Versions of access are 2002 &
2003. The errors are userspecific and occur in both versions. The
SQL-Servers are accessed with an adp-file in 2002-format.
We have one usergroup which is member of specially many groups. This
affects the size of their windows access token which becomes constantly
larger. In order to enable those users to still access their mailboxes
on our Exchange servers, the DWORD entry "MaxTokenSize" with the
decimal value "65535" was made to the newly created key "Parameters" of
their registry branch
"HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos ".
Since then those users can not access any of our SQL Servers using the
windows authentification. One of them gets the error
"[DBNETLIB][ConnectionRead(recv().] General network error. Check your
network documentation.", the others the error "Check connection:
Failed: Cannot generate SSPI context".
In case of resetting the registry entries (by deleting them), the one
user receives the same error message as the rest while it doesn't make
any difference to those (but at least they can't connect to their
mailboxes).
After having researched the web, I realised in one of the SQL-Servers
logfiles the entry "Invalid buffer received from client.." which lead
me to start to believe it could have to do something with the kerberos
encryption in the first place. Therefore I asked if changes to the
tokensize had been made. I applied the change with "EXEC sp_configure
'network packet size', 65535 RECONFIGURE" on our testsystem and "EXEC
sp_configure" confirms that the value is run.
Consequence: The entry in the SQL Server log doesn't appear any longer, but the users still receive their error messages.
Do you have any hints?
Your comments will be highly appreciated!
Regards,
caracol
Hi, CaraCol
Your case seems interesting. The error you hit is very general and could has various causes. So, please first check following blogs to see whether they resolved your problem:
http://blogs.msdn.com/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/15/481297.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx
http://blogs.msdn.com/sql_protocols/archive/2007/01/02/cannot-generate-sspi-context-error-message-poisoned-dns.aspx
If they not, can you provide more detail answer about your system configuration by fllowing up the guideline:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1
Thanks!
Ming
|||Hi Ming,thanks for your informationsites. I had already tried out parts of it but reviewed them all the same.
The SPN does work correctly, otherwise our other usersgroups wouldn't be able to connect to our servers. I double checked this by setspn -l domain\accountname and got the desired result on the rigth port.
When turning on Named Pipes and restarting the instance on the serverside while activating NP on the clientside only (cliconfig.exe), we get the error message "Error on testing the connection while initialising the provider. [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied" (My error messages are translated from our german clients).
We are running SQL Servers 2000 Standard English Edition (8.00.760 SP3) on English W2k servers with SP4 and we use named instances with TCP/IP only.
Our clients are WinXP Pro with SP2 and Access 2002 (MDAC 2.70.7713.0) or Access 2003 (MDAC 2.81.1117.0). Connection is made by Access.
Aliases are not existent.
The service account is a domain administrator.
Service of WinXP SP2 Firewall is deaktivated or the firewall is configured as inactive.
There is no encryption enforcement.
Users are local admins.
We have installed Trend Micro Server Protect / Antivir Corporate Edition 5.58 respectively on every machine. A firewall is not provided by this version.
The Clients are shut down every day, so I doubt deleting the cached credentials when they should be deleted after every restart would make any difference.
Do you have any ohter hints?
Thanks again.
Regards,
caracol|||
Hi, Caracol
Sorry, I am confused the error you came across, is it "Can not generate SSPI Context" or " General Network Error"? If it is the latter, [DBNETLIB][ConnectionRead (recv()) indicates connection failed during your DB operation, so, please try
1) http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx
2) Open SQL Server Profile, repro the issue, see which specific client operation caused the failure, also, check server ERRORLOG or EventLog to find clue.
3) What if you enable NP on the SQL Server, and make np connection from client, see whether same issue occured? Or at least whether the "SSPI Context" error persist?, If so, that might due to your domain configuration issue.
BTW, It'd better upgrade your SQL Server 2000 from SP3 to SP4, this might be a known issue in SP3 but fixed in SP4 or SQL 2005.
Good Luck!
Ming.
|||http://support.microsoft.com/kb/814401
http://www.sqlservercentral.com/columnists/cmiller/cannotgeneratesspicontext.asp
|||Hi Satya,thanks for your interest, but your links are just some of the standard ones I came over a dozen times.
Regards,
caracol|||Hi Ming,
thanks again for your enthusiasm.
As I described, I got different messages depending on the configuration.
TCP/IP:
Quote:
"Since then those users can not access any of our SQL Servers using the windows authentification. One of them gets the error "[DBNETLIB][ConnectionRead(recv().] General network error. Check your network documentation.", the others the error "Check connection: Failed: Cannot generate SSPI context"."
-> This ist the configuration I started with and where the error occured the first time.
NP:
Quote:
"When turning on Named Pipes and restarting the instance on the serverside while activating NP on the clientside only (cliconfig.exe), we get the error message "Error on testing the connection while initialising the provider. [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied" (My error messages are translated from our german clients)."
-> This is what I tried later on to see if changing access method might succeed.
I have no idea, why this specific user on TCP/IP gets the error "[DBNETLIB][ConnectionRead(recv().]" while the rest gets
"Check connection: Failed: Cannot generate SSPI context". It must have to do with the profile, though, as it doesn't matter on which client he's logged on.
Quote from your last answer:
{1) http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx }
-> I already got over this due to your post from 01-02-2007, it was one of the sublinks over there. Therefore, this info was not helpful this time.
{2) Open SQL Server Profile, repro the issue, see which specific client operation caused the failure, also, check server ERRORLOG or EventLog to find clue.}
-> Standard to revise the logs again, so not helpful. I described that the users can't even log in to SQL server any longer, and that access 2002 / 2003 is this client. It is nothing else than access' standard connection that doesn't work, nothing of specific client operation.
{3) What if you enable NP on the SQL Server, and make np connection from client, see whether same issue occured? Or at least whether the "SSPI Context" error persist?, If so, that might due to your domain configuration issue.}
-> I wrote that I already had tried out NP, again Quote:
"When turning on Named Pipes and restarting the instance on the serverside while activating NP on the clientside only (cliconfig.exe), we get the error message "Error on testing the connection while initialising the provider. [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied" (My error messages are translated from our german clients)." So, not helpful, as I already decribed which error the users get in this case.
{BTW, It'd better upgrade your SQL Server 2000 from SP3 to SP4, this might be a known issue in SP3 but fixed in SP4 or SQL 2005.}
-> Finally another idea, thanks. As we have one version on every server worldwide, I'm in no possition to just install SP4 on one or a few of them, but I'll make the proposition to upgrade worldwide to SP4. We'll at least try this out in our test environment and see if it is of any help, although {"this might be a known issue in SP3 but fixed in SP4 or SQL 2005"} is not what commercial operations consider to be trustworthy or even professional. (This is meant as hint for MS, not to you personally.)
Nevertheless, I thank you very much for taking your time again to try to assist me.
Regards,
caracol
Friday, March 23, 2012
MonthName function in IIF
We are getting a runtime #error when using MonthName in an IIF function more
than once as follows:
IIF(Parameters!ReportPeriod.Value <
7,MonthName(Parameters!ReportPeriod.Value +
6),MonthName(Parameters!ReportPeriod.Value))
Parameters!ReportPeriod is an integer, and the expression works Ok until the
second MonthName is added.
Thanks,
MattDoes this work (by adding an explicit cast)?
= IIF(Parameters!ReportPeriod.Value > 7,
MonthName(Parameters!ReportPeriod.Value + 6),
MonthName(CInt(Parameters!ReportPeriod.Value)))
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:E9371099-FDAB-4A79-95D5-8344C8595347@.microsoft.com...
> Hi,
> We are getting a runtime #error when using MonthName in an IIF function
> more
> than once as follows:
> IIF(Parameters!ReportPeriod.Value <
> 7,MonthName(Parameters!ReportPeriod.Value +
> 6),MonthName(Parameters!ReportPeriod.Value))
> Parameters!ReportPeriod is an integer, and the expression works Ok until
> the
> second MonthName is added.
> Thanks,
> Matt|||Thanks - that works Ok.
"Robert Bruckner [MSFT]" wrote:
> Does this work (by adding an explicit cast)?
> = IIF(Parameters!ReportPeriod.Value > 7,
> MonthName(Parameters!ReportPeriod.Value + 6),
> MonthName(CInt(Parameters!ReportPeriod.Value)))
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:E9371099-FDAB-4A79-95D5-8344C8595347@.microsoft.com...
> > Hi,
> > We are getting a runtime #error when using MonthName in an IIF function
> > more
> > than once as follows:
> >
> > IIF(Parameters!ReportPeriod.Value <
> > 7,MonthName(Parameters!ReportPeriod.Value +
> > 6),MonthName(Parameters!ReportPeriod.Value))
> >
> > Parameters!ReportPeriod is an integer, and the expression works Ok until
> > the
> > second MonthName is added.
> >
> > Thanks,
> > Matt
>
>sql
Monday, March 19, 2012
Monitoring SQL Server Error Message - Severity Level Messages
Do SQL server error messages (severilty level messages 11-16 & 17-25),
both 2000 & 2005, get written to the Windows Application Log, as well
as, the SQL server error log? I mainly monitor the server externally
(Windows Event Logs) and would like to NOT have to configure a MAPI
client on SQL to receive the SQL server severity errors.
Thanks,
Dan
The ones that are written to the errorlog are also written to the eventlog.
However, whether an error is to be written to eventlog/errorlog depends on whether it is configured
to do so. In 2000, sysmessages table, check the dlevel column. In 2005, check sys.messages. In 2000,
you can specify whether an error is to be logged (using sp_altermessage), but not in 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"danfoxley@.anon.postalias" <danfoxley@.gmail.com> wrote in message
news:1187251441.579647.169310@.i38g2000prf.googlegr oups.com...
> Hello,
> Do SQL server error messages (severilty level messages 11-16 & 17-25),
> both 2000 & 2005, get written to the Windows Application Log, as well
> as, the SQL server error log? I mainly monitor the server externally
> (Windows Event Logs) and would like to NOT have to configure a MAPI
> client on SQL to receive the SQL server severity errors.
> Thanks,
> Dan
>
Monitoring SQL Server Error Message - Severity Level Messages
Do SQL server error messages (severilty level messages 11-16 & 17-25),
both 2000 & 2005, get written to the Windows Application Log, as well
as, the SQL server error log? I mainly monitor the server externally
(Windows Event Logs) and would like to NOT have to configure a MAPI
client on SQL to receive the SQL server severity errors.
Thanks,
DanThe ones that are written to the errorlog are also written to the eventlog.
However, whether an error is to be written to eventlog/errorlog depends on whether it is configured
to do so. In 2000, sysmessages table, check the dlevel column. In 2005, check sys.messages. In 2000,
you can specify whether an error is to be logged (using sp_altermessage), but not in 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"danfoxley@.anon.postalias" <danfoxley@.gmail.com> wrote in message
news:1187251441.579647.169310@.i38g2000prf.googlegroups.com...
> Hello,
> Do SQL server error messages (severilty level messages 11-16 & 17-25),
> both 2000 & 2005, get written to the Windows Application Log, as well
> as, the SQL server error log? I mainly monitor the server externally
> (Windows Event Logs) and would like to NOT have to configure a MAPI
> client on SQL to receive the SQL server severity errors.
> Thanks,
> Dan
>
Monitoring SQL Server Error Message - Severity Level Messages
Do SQL server error messages (severilty level messages 11-16 & 17-25),
both 2000 & 2005, get written to the Windows Application Log, as well
as, the SQL server error log? I mainly monitor the server externally
(Windows Event Logs) and would like to NOT have to configure a MAPI
client on SQL to receive the SQL server severity errors.
Thanks,
DanThe ones that are written to the errorlog are also written to the eventlog.
However, whether an error is to be written to eventlog/errorlog depends on w
hether it is configured
to do so. In 2000, sysmessages table, check the dlevel column. In 2005, chec
k sys.messages. In 2000,
you can specify whether an error is to be logged (using sp_altermessage), bu
t not in 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"danfoxley@.anon.postalias" <danfoxley@.gmail.com> wrote in message
news:1187251441.579647.169310@.i38g2000prf.googlegroups.com...
> Hello,
> Do SQL server error messages (severilty level messages 11-16 & 17-25),
> both 2000 & 2005, get written to the Windows Application Log, as well
> as, the SQL server error log? I mainly monitor the server externally
> (Windows Event Logs) and would like to NOT have to configure a MAPI
> client on SQL to receive the SQL server severity errors.
> Thanks,
> Dan
>
Monitoring SQL Server Error logs
We have a large number of SQL servers that we are supporting. Monitoring the
error logs for new errors is really a big task as we have to manually check
these error logs. I was hoping that some of you might have automated this
process and filtered out the unwanted messages from the error log and mail
only the genuine ones. If anyone can share it with the group, it will be
terrific as you will be giving us extra minutes of sleep each night.
Thanking you in anticipation,
Yoga
You'll need to define for yourself what a wanted message is.
One option is to use finstr to search for whatever it is you
are looking for - you can find examples in these articles:
http://support.microsoft.com/?id=115519
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=40
You can automate those in a job.
Another consideration is how you set up and use your alerts
and monitoring on the servers. For most things you can be
notified if monitoring is set up correctly.
Of course there are a lot of third party solutions but I
take it your looking for scripts and built in solutions.
-Sue
On Mon, 26 Mar 2007 11:53:38 -0700, "Yoganarasimha Prasad"
<yogakiran@.gmail.com> wrote:
>Hi,
>We have a large number of SQL servers that we are supporting. Monitoring the
>error logs for new errors is really a big task as we have to manually check
>these error logs. I was hoping that some of you might have automated this
>process and filtered out the unwanted messages from the error log and mail
>only the genuine ones. If anyone can share it with the group, it will be
>terrific as you will be giving us extra minutes of sleep each night.
>Thanking you in anticipation,
>Yoga
>
Monitoring SQL Server Error logs
We have a large number of SQL servers that we are supporting. Monitoring the
error logs for new errors is really a big task as we have to manually check
these error logs. I was hoping that some of you might have automated this
process and filtered out the unwanted messages from the error log and mail
only the genuine ones. If anyone can share it with the group, it will be
terrific as you will be giving us extra minutes of sleep each night.
Thanking you in anticipation,
YogaYou'll need to define for yourself what a wanted message is.
One option is to use finstr to search for whatever it is you
are looking for - you can find examples in these articles:
http://support.microsoft.com/?id=115519
http://www.sqlservercentral.com/scr...asp?scriptid=40
You can automate those in a job.
Another consideration is how you set up and use your alerts
and monitoring on the servers. For most things you can be
notified if monitoring is set up correctly.
Of course there are a lot of third party solutions but I
take it your looking for scripts and built in solutions.
-Sue
On Mon, 26 Mar 2007 11:53:38 -0700, "Yoganarasimha Prasad"
<yogakiran@.gmail.com> wrote:
>Hi,
>We have a large number of SQL servers that we are supporting. Monitoring th
e
>error logs for new errors is really a big task as we have to manually check
>these error logs. I was hoping that some of you might have automated this
>process and filtered out the unwanted messages from the error log and mail
>only the genuine ones. If anyone can share it with the group, it will be
>terrific as you will be giving us extra minutes of sleep each night.
>Thanking you in anticipation,
>Yoga
>|||I've got a DIY SQL error log checking , as you can see in the script there a
various terms filtered out , change it as required.
I've selected those terms , as error logs I'm not interested in. It takes a
parameter , being the server name . I've got it wrapped on another sp that
runs through the servers , hitting the the error log sp , and then if
relevant send an email
http://www.quicksqlserver.com/2007/...erver_log_.html
Jack Vamvas
___________________________________
Advertise your IT vacancies for free at - http://www.ITjobfeed.com
"Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
news:elZrRg9bHHA.1388@.TK2MSFTNGP05.phx.gbl...
> Hi,
> We have a large number of SQL servers that we are supporting. Monitoring
> the error logs for new errors is really a big task as we have to manually
> check these error logs. I was hoping that some of you might have automated
> this process and filtered out the unwanted messages from the error log and
> mail only the genuine ones. If anyone can share it with the group, it will
> be terrific as you will be giving us extra minutes of sleep each night.
> Thanking you in anticipation,
> Yoga
>
Monitoring SQL Server Error logs
We have a large number of SQL servers that we are supporting. Monitoring the
error logs for new errors is really a big task as we have to manually check
these error logs. I was hoping that some of you might have automated this
process and filtered out the unwanted messages from the error log and mail
only the genuine ones. If anyone can share it with the group, it will be
terrific as you will be giving us extra minutes of sleep each night.
Thanking you in anticipation,
YogaYou'll need to define for yourself what a wanted message is.
One option is to use finstr to search for whatever it is you
are looking for - you can find examples in these articles:
http://support.microsoft.com/?id=115519
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=40
You can automate those in a job.
Another consideration is how you set up and use your alerts
and monitoring on the servers. For most things you can be
notified if monitoring is set up correctly.
Of course there are a lot of third party solutions but I
take it your looking for scripts and built in solutions.
-Sue
On Mon, 26 Mar 2007 11:53:38 -0700, "Yoganarasimha Prasad"
<yogakiran@.gmail.com> wrote:
>Hi,
>We have a large number of SQL servers that we are supporting. Monitoring the
>error logs for new errors is really a big task as we have to manually check
>these error logs. I was hoping that some of you might have automated this
>process and filtered out the unwanted messages from the error log and mail
>only the genuine ones. If anyone can share it with the group, it will be
>terrific as you will be giving us extra minutes of sleep each night.
>Thanking you in anticipation,
>Yoga
>|||I've got a DIY SQL error log checking , as you can see in the script there a
various terms filtered out , change it as required.
I've selected those terms , as error logs I'm not interested in. It takes a
parameter , being the server name . I've got it wrapped on another sp that
runs through the servers , hitting the the error log sp , and then if
relevant send an email
http://www.quicksqlserver.com/2007/03/sql_server_log_.html
Jack Vamvas
___________________________________
Advertise your IT vacancies for free at - http://www.ITjobfeed.com
"Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
news:elZrRg9bHHA.1388@.TK2MSFTNGP05.phx.gbl...
> Hi,
> We have a large number of SQL servers that we are supporting. Monitoring
> the error logs for new errors is really a big task as we have to manually
> check these error logs. I was hoping that some of you might have automated
> this process and filtered out the unwanted messages from the error log and
> mail only the genuine ones. If anyone can share it with the group, it will
> be terrific as you will be giving us extra minutes of sleep each night.
> Thanking you in anticipation,
> Yoga
>
monitoring sql error log for keywords
We have Patrol monitoring running on our SQL Server 2000/2005 instances.
One of the alerts for Patrol is ErrorLogUpdates.
This sends out an alert when a particular keyword is found in the error log.
There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
I have been taking a look at quiet a few of our error logs and not making
any headway so far.
Does anyone have any suggestions as to what I can put in INCLUDE list and
EXCLUDE list of keywords to look for in SQL error log.
Thanks in advance.
Cheers.
Kunal.
Hi
Products like MOM come with preconfigured scripts, therefore I would expect
the software vendor to supply this.
John
"kunalap" wrote:
> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.
|||First, you really have to determine what you want to be alerted on. For
instance, we monitor all the SQL errors with severity 17 or higher, backup
failure, port binding failure, restarts, and so on. Each of rthese error
types has a certain patterns that you can use. Unfortunately, MS has not been
very good at keeping the error messages consistent on many dimensions, making
life somewhat difficult.
Anyway, for port binding failure for instance, you can look for the
following text string; "SuperSocket Info: Bind failed on TCP port", and for
severe SQL errors, you may want to enumerate all the patterns like "Severity:
17", replacing 17 with 18, 19, 20, and so on. Patrol has a perl like language
and should be very easy to specific a regular expression pattern here.
Linchi
"kunalap" wrote:
> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.
monitoring sql error log for keywords
We have Patrol monitoring running on our SQL Server 2000/2005 instances.
One of the alerts for Patrol is ErrorLogUpdates.
This sends out an alert when a particular keyword is found in the error log.
There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
I have been taking a look at quiet a few of our error logs and not making
any headway so far.
Does anyone have any suggestions as to what I can put in INCLUDE list and
EXCLUDE list of keywords to look for in SQL error log.
Thanks in advance.
Cheers.
Kunal.Hi
Products like MOM come with preconfigured scripts, therefore I would expect
the software vendor to supply this.
John
"kunalap" wrote:
> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.|||First, you really have to determine what you want to be alerted on. For
instance, we monitor all the SQL errors with severity 17 or higher, backup
failure, port binding failure, restarts, and so on. Each of rthese error
types has a certain patterns that you can use. Unfortunately, MS has not been
very good at keeping the error messages consistent on many dimensions, making
life somewhat difficult.
Anyway, for port binding failure for instance, you can look for the
following text string; "SuperSocket Info: Bind failed on TCP port", and for
severe SQL errors, you may want to enumerate all the patterns like "Severity:
17", replacing 17 with 18, 19, 20, and so on. Patrol has a perl like language
and should be very easy to specific a regular expression pattern here.
Linchi
"kunalap" wrote:
> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.
Wednesday, March 7, 2012
monitor replication
How do I automate the successful / error working of
replication - both transactional as well as merge. Is
there any system tables based on which i can do a join?
Appreciate if someone can provide a query...
regards.
bharathIf you want to monitor replication you need to query information from the
table
sysjobs and sysjobhistory table in MSDB database.
In sysjobs the name of the job would be like this
<Remote Server Name>-<Publication name>-<Publication database>-<Local sql
server name>-<Database name>- 0
For this particular job name find the job_id and using it query the table
sysjobhistory. Watch for the columns step_name and message.
Regards,
Jagan Mohan
MCP
"bharath" <barathsing@.hotmail.com> wrote in message
news:051401c3b7e0$b3f08eb0$a401280a@.phx.gbl...
> Hi,
> How do I automate the successful / error working of
> replication - both transactional as well as merge. Is
> there any system tables based on which i can do a join?
> Appreciate if someone can provide a query...
> regards.
> bharath
>
>|||One method I have always been using and have found to be very effective and
simple is to create an end-to-end trace myself and then monitor the trace
for the end-to-end transactional replication deplay.
To create such a trace, I include a dummy table in every publication. The
dummy table has a datetime column and I schedule a job to update the dummy
table at a regular interval. Then, when the change in the dummy table has
reached the subscriber via replication, I compare the the time the datetime
is updated at the publisher and the time the same row is updated at the
subscriber. The time difference gives me the end-to-end replication deplay.
I can then send alerts if the deplay is longer than a certain threshold.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"bharath" <barathsing@.hotmail.com> wrote in message
news:051401c3b7e0$b3f08eb0$a401280a@.phx.gbl...
> Hi,
> How do I automate the successful / error working of
> replication - both transactional as well as merge. Is
> there any system tables based on which i can do a join?
> Appreciate if someone can provide a query...
> regards.
> bharath
>
>
Monday, February 20, 2012
Money format error
I use asp.net 2.0 and sql server 2005 for a web site (and Microsoft enterprise library).When I run aplication at local there is no problem but at the server I take this error:
Disallowed implicit conversion from data type varchar to data type money, table 'dbname.dbo.shopProducts', column 'productPrice'. Use the CONVERT function to run this query.
productPrice coloumn format is money. It was working correctly my old server but now it crashed.How can I solve this problem? And why it isn't work same configuration?
My code:
decimal productPrice;
Database db =DatabaseFactory.CreateDatabase("connection");
string sqlCommand ="update shopProducts set .................,productPrice='" + productPrice.ToString().Replace(",",".") +"',................where productID=" + productID +" ";
db.ExecuteNonQuery(CommandType.Text, sqlCommand)
Decimal should be able to covert to SqlMoney implicitly, why you convert the price to string before update it to the table? However, it's better to useParameterized Queries as possible as you can.
money datatype
value. If i try to enter a null value from my asp page i
am getting error... what i need to do on my sql server
table so it does not error me out. i think, it has
something to do with precision and scale... but I don't
know what.
ERROR:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
Incorrect syntax near ','.
ThanksCould you display the string that you are constructing in your application?
Look at this string when the money column is null. I am sure you will know
what's causing the problem. It just looks like you are concatenating
something with NULL and the whole thing becomes NULL.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"eren" <oeren@.calcoastcu.org> wrote in message
news:004c01c37d37$d3bd55e0$a401280a@.phx.gbl...
i have money a datatype in my table and it allows null
value. If i try to enter a null value from my asp page i
am getting error... what i need to do on my sql server
table so it does not error me out. i think, it has
something to do with precision and scale... but I don't
know what.
ERROR:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
Incorrect syntax near ','.
Thanks|||This looks like a syntax error in the statement generated by the asp page.
Verify that the statement is correct and that nulls are handled correctly by
the asp code generating the statement.
Shaun
"eren" <oeren@.calcoastcu.org> wrote in message
news:004c01c37d37$d3bd55e0$a401280a@.phx.gbl...
> i have money a datatype in my table and it allows null
> value. If i try to enter a null value from my asp page i
> am getting error... what i need to do on my sql server
> table so it does not error me out. i think, it has
> something to do with precision and scale... but I don't
> know what.
> ERROR:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near ','.
> Thanks
MOM Subscription errors
set up a new subscription. I have previously been able to subscribe to
the reports, but now we get this error.
"There is an error in XML document (1,50623)"
I have seen couple of other posts on this, but never an answer or
solution. I can open and run the report in Visual Studio, but even if I
republish them to another folder they still fail. I can see the error
in the logs telling me I have an illegal character, but other than
validating the error, the log does not provide useful info.
THis is happening on more than one MOM report, but only on MOM reports.
Anyone know what is happening'?Had to contact MS. Of course there is a bug that requires a HOT FIX
that needs to be run on the MOM server. Turns out somehow there are
non-printable characters being populated in the data the reports are
using for paramaters to the reports.
The RS log files shows that there is an illegal character but does not
tell you where it is. I finally stumbled upon the illegal character
when looking at the drop down list boxes on the reports. They are of
course non-printable characters so you will not see them in the results
of a SQL select statement.
Here is the article that outlines the problem.
http://support.microsoft.com/?id=915785#XSLTH3120121123120121120120
Article ID : 915785
MOM 2005 Reporting error
Hi
I m using MOM 2005 SP1 FR with MSSQL 2000 SP3 and i get this error on one of my reports :
Erreur de Reporting Services
--
Une erreur s'est produite lors du traitement du rapport. (rsProcessingAborted) Obtenir de l'aide en ligne
Impossible de lire la ligne de donnes suivante pour le dataset PerfAnalysis. (rsErrorReadingNextDataRow) Obtenir de l'aide en ligne
La conversion d'un type de donnes CHAR en type DATETIME a donn une valeur hors des limites des valeurs de date et d'heure.
--
Microsoft Reporting Services
What can i do, i think i must edit xml file ?
Regards.
I have exactly the same problem !Did anyone have an idea ?
Regards.
MOM 2005 Reporting error
Hi
I m using MOM 2005 SP1 FR with MSSQL 2000 SP3 and i get this error on one of my reports :
Erreur de Reporting Services
--
Une erreur s'est produite lors du traitement du rapport. (rsProcessingAborted) Obtenir de l'aide en ligne
Impossible de lire la ligne de donnes suivante pour le dataset PerfAnalysis. (rsErrorReadingNextDataRow) Obtenir de l'aide en ligne
La conversion d'un type de donnes CHAR en type DATETIME a donn une valeur hors des limites des valeurs de date et d'heure.
--
Microsoft Reporting Services
What can i do, i think i must edit xml file ?
Regards.
I have exactly the same problem !Did anyone have an idea ?
Regards.