I have a communication error from my client when I try to connect to my SQL
server 2000 SP4 on a Windows 2003 server. Is there any method that I can get
to see if I don't miss something when I have made the installation on the
server part ?
Every help will be welcome
Regards,
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...curity/200609/1I dont believe that SQL server keeps track of that type of information
unless you have C2 auditing enabled. You could also pick that up in a trace
file had you been tracing.
http://www.microsoft.com/technet/pr...tain/sqlc2.mspx
I could be wrong though. Does anyone else have any information?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Silver via droptable.com" <u26873@.uwe> wrote in message
news:669141b5c2b48@.uwe...
>I have a communication error from my client when I try to connect to my SQL
> server 2000 SP4 on a Windows 2003 server. Is there any method that I can
> get
> to see if I don't miss something when I have made the installation on the
> server part ?
> Every help will be welcome
> Regards,
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...curity/200609/1
>sql
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Thursday, March 22, 2012
Couldn't call a procedure
Hi,
I am using MSSQL-2000. I couldn't call a procedure from a client (windows
98) but its working fine when i call it from window2000 system.
What is the reason for this?
Thanks,
SouraHi,
This will not happen. Even from client you are loging into SQL Server
machine using some tools.
Could you please exactly say how you are calling the procedure.
Thanks
Hari
SQL SERVER MVP
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:0F6D09C0-7057-4651-AEFF-A18C73691659@.microsoft.com...
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>|||Hi
Please tell us what is the authentication that u are using.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"SouRa" wrote:
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>
I am using MSSQL-2000. I couldn't call a procedure from a client (windows
98) but its working fine when i call it from window2000 system.
What is the reason for this?
Thanks,
SouraHi,
This will not happen. Even from client you are loging into SQL Server
machine using some tools.
Could you please exactly say how you are calling the procedure.
Thanks
Hari
SQL SERVER MVP
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:0F6D09C0-7057-4651-AEFF-A18C73691659@.microsoft.com...
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>|||Hi
Please tell us what is the authentication that u are using.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"SouRa" wrote:
> Hi,
> I am using MSSQL-2000. I couldn't call a procedure from a client (windows
> 98) but its working fine when i call it from window2000 system.
> What is the reason for this?
> Thanks,
> Soura
>
>
Tuesday, March 20, 2012
Could not start SQL Server
SQL server is not starting, logs following error in
windows log
Error: 9003, Severity: 20,State: 1
The LSN (4:482:1) passed to log scan in database 'model'
is invalid
Is any one having solution for this?Manoj
It looks like the model database has become corrupted due to the power
failure.
Try to start the SQL Server as an application from a command prompt. For
more information, please refer to the topics: 'Starting SQL Server
Manually' and 'Using Startup Options' on Microsoft SQL Server Books Online.
Look if it does not help you so in this situation your best bet is to call
MS PSS
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Hi,
Seems your Model database is corrupt,
1. Stop SQL server
2. Copy the .MDF and .LDF files (Belongs to MODEL database) to a different
ent location
3. From a different SQL Serevr copy the Model databases .MDF and .LDF files
to the same folder. Overwrite the old files
4. Now start the SQL server.
Most probably this will work out.
Thanks
Hari
MCDBA
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Thanks Hari !! I will try this option
>--Original Message--
>Hi,
>Seems your Model database is corrupt,
>1. Stop SQL server
>2. Copy the .MDF and .LDF files (Belongs to MODEL
database) to a different
>ent location
>3. From a different SQL Serevr copy the Model
databases .MDF and .LDF files
>to the same folder. Overwrite the old files
>4. Now start the SQL server.
>
>Most probably this will work out.
>Thanks
>Hari
>MCDBA
>
>"Manoj" <manoj_raheja@.hotmail.com> wrote in message
>news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
>> SQL server is not starting, logs following error in
>> windows log
>> Error: 9003, Severity: 20,State: 1
>> The LSN (4:482:1) passed to log scan in database 'model'
>> is invalid
>> Is any one having solution for this?
>
>.
>|||Make sure that other SQL Server has the same collation. SQL Server does not
support different collations across the system databases.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<anonymous@.discussions.microsoft.com> wrote in message
news:d07801c3eeee$ed440170$a401280a@.phx.gbl...
> Thanks Hari !! I will try this option
> >--Original Message--
> >Hi,
> >
> >Seems your Model database is corrupt,
> >
> >1. Stop SQL server
> >2. Copy the .MDF and .LDF files (Belongs to MODEL
> database) to a different
> >ent location
> >3. From a different SQL Serevr copy the Model
> databases .MDF and .LDF files
> >to the same folder. Overwrite the old files
> >4. Now start the SQL server.
> >
> >
> >Most probably this will work out.
> >
> >Thanks
> >Hari
> >MCDBA
> >
> >
> >"Manoj" <manoj_raheja@.hotmail.com> wrote in message
> >news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> >> SQL server is not starting, logs following error in
> >> windows log
> >>
> >> Error: 9003, Severity: 20,State: 1
> >> The LSN (4:482:1) passed to log scan in database 'model'
> >> is invalid
> >>
> >> Is any one having solution for this?
> >>
> >
> >
> >.
> >|||Hi! Hari Prasad,
Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||What's the error? Could you post the error form the error log?
--
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide SQL Community)
SQLTips, SQL Scripts, SQL Forums, SQL Articles, SQL Radio, SQL Server 2008,
SQL Blogs, SQL Clinic and a lot of SQL Server fun.
"Girish Sharma (QA Engg.)" wrote:
> Hi! Hari Prasad,
> Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
>
> From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>
windows log
Error: 9003, Severity: 20,State: 1
The LSN (4:482:1) passed to log scan in database 'model'
is invalid
Is any one having solution for this?Manoj
It looks like the model database has become corrupted due to the power
failure.
Try to start the SQL Server as an application from a command prompt. For
more information, please refer to the topics: 'Starting SQL Server
Manually' and 'Using Startup Options' on Microsoft SQL Server Books Online.
Look if it does not help you so in this situation your best bet is to call
MS PSS
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Hi,
Seems your Model database is corrupt,
1. Stop SQL server
2. Copy the .MDF and .LDF files (Belongs to MODEL database) to a different
ent location
3. From a different SQL Serevr copy the Model databases .MDF and .LDF files
to the same folder. Overwrite the old files
4. Now start the SQL server.
Most probably this will work out.
Thanks
Hari
MCDBA
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Thanks Hari !! I will try this option
>--Original Message--
>Hi,
>Seems your Model database is corrupt,
>1. Stop SQL server
>2. Copy the .MDF and .LDF files (Belongs to MODEL
database) to a different
>ent location
>3. From a different SQL Serevr copy the Model
databases .MDF and .LDF files
>to the same folder. Overwrite the old files
>4. Now start the SQL server.
>
>Most probably this will work out.
>Thanks
>Hari
>MCDBA
>
>"Manoj" <manoj_raheja@.hotmail.com> wrote in message
>news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
>> SQL server is not starting, logs following error in
>> windows log
>> Error: 9003, Severity: 20,State: 1
>> The LSN (4:482:1) passed to log scan in database 'model'
>> is invalid
>> Is any one having solution for this?
>
>.
>|||Make sure that other SQL Server has the same collation. SQL Server does not
support different collations across the system databases.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<anonymous@.discussions.microsoft.com> wrote in message
news:d07801c3eeee$ed440170$a401280a@.phx.gbl...
> Thanks Hari !! I will try this option
> >--Original Message--
> >Hi,
> >
> >Seems your Model database is corrupt,
> >
> >1. Stop SQL server
> >2. Copy the .MDF and .LDF files (Belongs to MODEL
> database) to a different
> >ent location
> >3. From a different SQL Serevr copy the Model
> databases .MDF and .LDF files
> >to the same folder. Overwrite the old files
> >4. Now start the SQL server.
> >
> >
> >Most probably this will work out.
> >
> >Thanks
> >Hari
> >MCDBA
> >
> >
> >"Manoj" <manoj_raheja@.hotmail.com> wrote in message
> >news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> >> SQL server is not starting, logs following error in
> >> windows log
> >>
> >> Error: 9003, Severity: 20,State: 1
> >> The LSN (4:482:1) passed to log scan in database 'model'
> >> is invalid
> >>
> >> Is any one having solution for this?
> >>
> >
> >
> >.
> >|||Hi! Hari Prasad,
Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||What's the error? Could you post the error form the error log?
--
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide SQL Community)
SQLTips, SQL Scripts, SQL Forums, SQL Articles, SQL Radio, SQL Server 2008,
SQL Blogs, SQL Clinic and a lot of SQL Server fun.
"Girish Sharma (QA Engg.)" wrote:
> Hi! Hari Prasad,
> Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
>
> From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>
Could not start SQL Agent
Hello.
I have SQL Server MSDE running Windows 2000.
When I start SQL Agent gives me the following error:"Could not start
the SQLAgent$SPSQL service on Local Computer. The service did not
return an error..."
An
Can anyone help me?
Thanks.
ticha
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message930459.html
Hi
Look in the Windows Event Log and the Agent log file in the LOGs directory.
You may get more information there.
Regards
Mike
"ticha" wrote:
> Hello.
> I have SQL Server MSDE running Windows 2000.
> When I start SQL Agent gives me the following error:"Could not start
> the SQLAgent$SPSQL service on Local Computer. The service did not
> return an error..."
> An
> Can anyone help me?
> Thanks.
>
> --
> ticha
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message930459.html
>
I have SQL Server MSDE running Windows 2000.
When I start SQL Agent gives me the following error:"Could not start
the SQLAgent$SPSQL service on Local Computer. The service did not
return an error..."
An
Can anyone help me?
Thanks.
ticha
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message930459.html
Hi
Look in the Windows Event Log and the Agent log file in the LOGs directory.
You may get more information there.
Regards
Mike
"ticha" wrote:
> Hello.
> I have SQL Server MSDE running Windows 2000.
> When I start SQL Agent gives me the following error:"Could not start
> the SQLAgent$SPSQL service on Local Computer. The service did not
> return an error..."
> An
> Can anyone help me?
> Thanks.
>
> --
> ticha
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message930459.html
>
Monday, March 19, 2012
could not obtain information about...
I am getting the following message in my event logs since hitting windows up
date and installing, among others SP4 for win2k.
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Michaels B
ackup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) - Status: Failed - Invoked
on: 2004-01-19 02:00:00 - Message: The job failed. Unable to determine if
the owner (MYSERVER\mylogin) of job DB Backup Job for DB Maintenance Plan 'M
ichaels Backup Plan' has server access (reason: Could not obtain information
about Windows NT group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 819
8))."
the only thing that changed was the updates, which can be significant but I
certainly didn't change anything related to my account. I have recreated th
e plan with the same result.
I can open the LOGON section of SQLadmin and see my name there, I can open i
t and close it but if I try to make any changes it says messages similar to
the above on.
KB articles suggested ading the everyone group to the pre2000 users group bu
t that sounds dangerous.
Help? what else can I look at. I am the sysop and should have all the necess
ary rightsIn message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
writes
I assume you have seen KB 241643, but have you tried the first
workaround "Change the job owner to a standard SQL Server user or system
administrator (sa)."? I have read this many times, and the second option
has never worked for me, so I go straight for option 1. I suspect there
may be other causes, perhaps network issues between SQL and the DC.
PRB: 8198 Error Message Returned from Job Owned by Windows NT
Authenticated User
http://support.microsoft.com?kbid=241643
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org|||"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...
I saw the KB article and I couldn't make option 2 work either so that is
encouraging :-?
The DC and the SQL server are the same machine so comms shouldn't be an
issue.
I'll try creating a new backup plan under sa but could you tell me what a
"Standard Sql Server User " is?
"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...
writes
A standard SQL Server user, or SQL (Server) login, is what you use as
opposed to and integrated or NT authentication login. This option is
only available if the server is set to Mixed Mode security.
sa is a SQL login, but BUILTIN\Administrators is a integrated login.
Make sense?
Darren
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org
date and installing, among others SP4 for win2k.
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Michaels B
ackup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) - Status: Failed - Invoked
on: 2004-01-19 02:00:00 - Message: The job failed. Unable to determine if
the owner (MYSERVER\mylogin) of job DB Backup Job for DB Maintenance Plan 'M
ichaels Backup Plan' has server access (reason: Could not obtain information
about Windows NT group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 819
8))."
the only thing that changed was the updates, which can be significant but I
certainly didn't change anything related to my account. I have recreated th
e plan with the same result.
I can open the LOGON section of SQLadmin and see my name there, I can open i
t and close it but if I try to make any changes it says messages similar to
the above on.
KB articles suggested ading the everyone group to the pre2000 users group bu
t that sounds dangerous.
Help? what else can I look at. I am the sysop and should have all the necess
ary rightsIn message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
writes
quote:
>I am getting the following message in my event logs since hitting windows
>update_and installing, among others _SP4 for win2k.
>"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
>'Michaels Backup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) -
>Status: Failed - Invoked on: 2004-01-19 02:00:00 - Message: The job
>failed._ Unable to determine if the owner (MYSERVER\mylogin) of job DB
>Backup Job for DB Maintenance Plan 'Michaels Backup Plan' has server
>access (reason: Could not obtain information about Windows NT
>group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 8198))."
>the only thing that changed was the updates, which can be significant but
>_I certainly didn't change anything related to my account. I have recreated
>the plan with the same result.
>I can open the LOGON section of SQLadmin and see my name there, I
>can open it and close it but if I try to make any changes it says messages
>similar to the above on.
>KB articles suggested ading the everyone group to the pre2000 users
>group but that sounds dangerous.
>Help? what else can I look at. I am the sysop and should have all the
>necessary rights
I assume you have seen KB 241643, but have you tried the first
workaround "Change the job owner to a standard SQL Server user or system
administrator (sa)."? I have read this many times, and the second option
has never worked for me, so I go straight for option 1. I suspect there
may be other causes, perhaps network issues between SQL and the DC.
PRB: 8198 Error Message Returned from Job Owned by Windows NT
Authenticated User
http://support.microsoft.com?kbid=241643
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org|||"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...
quote:|||Lets try that again.
> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>
I saw the KB article and I couldn't make option 2 work either so that is
encouraging :-?
The DC and the SQL server are the same machine so comms shouldn't be an
issue.
I'll try creating a new backup plan under sa but could you tell me what a
"Standard Sql Server User " is?
"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...
quote:|||In message <u1fxN$d4DHA.2612@.tk2msftngp13.phx.gbl>, mmac <no@.thanks.com>
> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>
writes
quote:
>Lets try that again.
>I saw the KB article and I couldn't make option 2 work either so that is
>encouraging :-?
>The DC and the SQL server are the same machine so comms shouldn't be an
>issue.
>I'll try creating a new backup plan under sa but could you tell me what a
>"Standard Sql Server User " is?
>
A standard SQL Server user, or SQL (Server) login, is what you use as
opposed to and integrated or NT authentication login. This option is
only available if the server is set to Mixed Mode security.
sa is a SQL login, but BUILTIN\Administrators is a integrated login.
Make sense?
Darren
quote:
>"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in messag
e
>news:7r2qD3R8WFEAFwOw@.sqldts.com...
>recreated
>messages
>
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org
Could not obtain information about Windows NT group/user .......error code 0x534...
== I asked this question directly to Remus and wanted to share the response to all of those people using this forum ==
We recently moved our database server from SQL Server 2000 to SQL Server 2005. All applications on our intranet development server stay the same [VS.NET 2003], but recently resources in our Dev DB server ran out of space. While doing a thorough investigation, I noticed ERRORLOG file was occupying about 35 Gig of HDD space. I immediately checked SQL Server error log and noticed an entry which says –
===========================================================================================
Date 7/7/2006 4:45:37 PM
Log SQL Server (Current - 7/7/2006 4:45:00 PM)
Source spid77s
Message
The activated proc [dbo].[SqlQueryNotificationStoredProcedure-5eaf8465-d0cb-4be7-93b6-44bb979dd41c] running on queue BW_Content.dbo.SqlQueryNotificationService-5eaf8465-d0cb-4be7-93b6-44bb979dd41c output the following: 'Could not obtain information about Windows NT group/user 'BWCINC\HoffK', error code 0x534.'
===========================================================================================
What is this SqlQueryNotificationService in my database? Is it a SQL Server 2005 thing? Why the same kind of stored procedure does not exist in other databases, but BW_Content? This error is getting repeated most probably every second and is filling up our server.
I believe our corporate IT people removed our domain accounts from BWCINC domain to BWCORP domain and probably some application which is using BWCINC\HoffK credential is getting errored out. I tried to locate this application and was not successful.
Is there anyway that I can stop this ERRORLOG from growing? How can I delete these log entries so that I can make space on our Hard Drive? Is there an easy way in SQL Server 2005 to locate which application is creating this error?
Response from Remus:
The 'SqlQueryNotificationService-...' is the service created by SqlDependency when you call SqlDependency.Start (). The problem you describe appears because the 'dbo' user of the database is mapped to the login that originally created this database. The SqlDependency created queue has an EXECUTE AS OWNER clause, owner is 'dbo' and therefore this is equivalent to an EXECUTE AS USER = 'dbo'. The error you see is reported by the domain controller when asked to give information about the original account 'dbo' mapps to (that is, BWCINC\HoffK'): Error code: (Win32) 0x534 (1332) - No mapping between account names and security IDs was done.
To solve the issue, change 'dbo' to match a correct login, using either sp_changedbowner or ALTER AUTHORIZATION ON DATABASE::[dbname] TO [somavalidlogin]
To find the databases that have this problem, run this query:
select name, suser_sname(owner_sid) from sys.databases
The databses that have the problem will show NULL on the second column.
A similar problem is described here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=65711&SiteID=1
To remove the entries, use sp_cycle_errorlog to force a new errorlog file, then delete the huge log file.
I executed ALTER AUTHORIZATION ON DATABASE::[BW_Content] TO [sa];
I got this error in SQL Error Log once and the growth of ERRORLOG was stopped.
===============================================================
Date 7/10/2006 1:16:55 PM
Log SQL Server (Current - 7/10/2006 1:17:00 PM)
Source spid20s
Message
The query notification dialog on conversation handle '{6BDE95F7-0EFB-DA11-9064-000C2921B41B}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-c15bb868-ed56-47d2-bf91-ce18b320989a' because it does not exist.</Description></Error>'.
===============================================================
Should I be concerned about this error?
Thanks
-Binoy
Thanks for sharing this!|||Binoy Sankar wrote:
I got this error in SQL Error Log once and the growth of ERRORLOG was stopped.
===============================================================
Date 7/10/2006 1:16:55 PM
Log SQL Server (Current - 7/10/2006 1:17:00 PM)Source spid20s
Message
The query notification dialog on conversation handle '{6BDE95F7-0EFB-DA11-9064-000C2921B41B}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-c15bb868-ed56-47d2-bf91-ce18b320989a' because it does not exist.</Description></Error>'.===============================================================
Should I be concerned about this error?
Don't worry abouyt it. The error means that the client disconnected and the temporary service was dropped before the notification was fired.
Thanks,
~ Remus
Could not obtain information
Hi All,
We've just recently changed/upgraded server boxes and went from Windows 2000
Server to Windows 2003 Server with
SQLServer 2000 sp4 installed on both. The Startup Service Account settings f
or both SQLServer and SQLServer
Agent is 'System Account'. On the original machine backups worked without a
flaw, but with the new machine I
receive the following error:
<<error from SQL Agent Error log>>
[298] SQLServer Error: 8198, Could not obtain information about Windows
NT group/user 'DOMAINNAME\username'.
[SQLSTATE 42000] (ConnIsLoginSysAdmin)
When remoted into the new machine with 'DOMAINNAME\username' and doing an "e
xec xp_logininfo
'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
<<error from Query Analyzer>>
Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
Could not obtain information about Windows NT group/user 'DOMAINNAME\usernam
e'.
I've looked at kb241643 and kb834124 and realize there is a workaround, but
this same account gets locked by AD
at least a couple of times a day when I try and use it to login to this and/
or other machines I administer (this
account is an admin account used strictly for administration purposes, I hav
e an individual account that I use
for my desktop and laptop). It seems to have began shortly after I had to ch
ange the password for this account.
I believe, the error and the lockout are related (my inexperience shows as I
do not have anything concrete to
make that assumption) so I would really like to know why this is happening a
nd how to correct it.
Thank you.
gdr
--
Gary D. Rezek
University Nerworking Systems and Services
South Dakota State UniversityHi,
Is both SQL box on same Domain ? are they have the same User Account in it ?
Have you set Password Policy for Account Lockout ?if so ,after how many
attempts it locks account ? i suspect that theirs is no such user ..
Regards
--
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"Gary D. Rezek" wrote:
> Hi All,
> We've just recently changed/upgraded server boxes and went from Windows 20
00 Server to Windows 2003 Server with
> SQLServer 2000 sp4 installed on both. The Startup Service Account settings
for both SQLServer and SQLServer
> Agent is 'System Account'. On the original machine backups worked without
a flaw, but with the new machine I
> receive the following error:
> <<error from SQL Agent Error log>>
> [298] SQLServer Error: 8198, Could not obtain information about Window
s NT group/user 'DOMAINNAME\username'.
> [SQLSTATE 42000] (ConnIsLoginSysAdmin)
> When remoted into the new machine with 'DOMAINNAME\username' and doing an
"exec xp_logininfo
> 'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
> <<error from Query Analyzer>>
> Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
> Could not obtain information about Windows NT group/user 'DOMAINNAME\usern
ame'.
> I've looked at kb241643 and kb834124 and realize there is a workaround, bu
t this same account gets locked by AD
> at least a couple of times a day when I try and use it to login to this an
d/or other machines I administer (this
> account is an admin account used strictly for administration purposes, I h
ave an individual account that I use
> for my desktop and laptop). It seems to have began shortly after I had to
change the password for this account.
> I believe, the error and the lockout are related (my inexperience shows as
I do not have anything concrete to
> make that assumption) so I would really like to know why this is happening
and how to correct it.
> Thank you.
> gdr
> --
> Gary D. Rezek
> university Nerworking Systems and Services
> South Dakota State University
>
>|||Hi Andy,
Yes both boxes are on the same domain and have the same user accounts in the
m. As far as I can tell the 2 boxes
are near identical with their setups. The AD guys have set a lockout policy
of 5 bad logins within 15 minutes
locks the account out for 15 minutes.
Thanks.
gdr
"Andy Davis" <activecrypt@.gmail.com> wrote in message news:873FAFB3-F604-45F4-913F-EAF6D2C0A
CA0@.microsoft.com...[vbcol=seagreen]
> Hi,
> Is both SQL box on same Domain ? are they have the same User Account in it
?
> Have you set Password Policy for Account Lockout ?if so ,after how many
> attempts it locks account ? i suspect that theirs is no such user ..
> Regards
> --
> Andy Davis
> Active Crypt Team
> ---SQL Server Encryption
> Decryption Software
> http://www.activecrypt.com
>
> "Gary D. Rezek" wrote:
>
We've just recently changed/upgraded server boxes and went from Windows 2000
Server to Windows 2003 Server with
SQLServer 2000 sp4 installed on both. The Startup Service Account settings f
or both SQLServer and SQLServer
Agent is 'System Account'. On the original machine backups worked without a
flaw, but with the new machine I
receive the following error:
<<error from SQL Agent Error log>>
[298] SQLServer Error: 8198, Could not obtain information about Windows
NT group/user 'DOMAINNAME\username'.
[SQLSTATE 42000] (ConnIsLoginSysAdmin)
When remoted into the new machine with 'DOMAINNAME\username' and doing an "e
xec xp_logininfo
'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
<<error from Query Analyzer>>
Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
Could not obtain information about Windows NT group/user 'DOMAINNAME\usernam
e'.
I've looked at kb241643 and kb834124 and realize there is a workaround, but
this same account gets locked by AD
at least a couple of times a day when I try and use it to login to this and/
or other machines I administer (this
account is an admin account used strictly for administration purposes, I hav
e an individual account that I use
for my desktop and laptop). It seems to have began shortly after I had to ch
ange the password for this account.
I believe, the error and the lockout are related (my inexperience shows as I
do not have anything concrete to
make that assumption) so I would really like to know why this is happening a
nd how to correct it.
Thank you.
gdr
--
Gary D. Rezek
University Nerworking Systems and Services
South Dakota State UniversityHi,
Is both SQL box on same Domain ? are they have the same User Account in it ?
Have you set Password Policy for Account Lockout ?if so ,after how many
attempts it locks account ? i suspect that theirs is no such user ..
Regards
--
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"Gary D. Rezek" wrote:
> Hi All,
> We've just recently changed/upgraded server boxes and went from Windows 20
00 Server to Windows 2003 Server with
> SQLServer 2000 sp4 installed on both. The Startup Service Account settings
for both SQLServer and SQLServer
> Agent is 'System Account'. On the original machine backups worked without
a flaw, but with the new machine I
> receive the following error:
> <<error from SQL Agent Error log>>
> [298] SQLServer Error: 8198, Could not obtain information about Window
s NT group/user 'DOMAINNAME\username'.
> [SQLSTATE 42000] (ConnIsLoginSysAdmin)
> When remoted into the new machine with 'DOMAINNAME\username' and doing an
"exec xp_logininfo
> 'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
> <<error from Query Analyzer>>
> Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
> Could not obtain information about Windows NT group/user 'DOMAINNAME\usern
ame'.
> I've looked at kb241643 and kb834124 and realize there is a workaround, bu
t this same account gets locked by AD
> at least a couple of times a day when I try and use it to login to this an
d/or other machines I administer (this
> account is an admin account used strictly for administration purposes, I h
ave an individual account that I use
> for my desktop and laptop). It seems to have began shortly after I had to
change the password for this account.
> I believe, the error and the lockout are related (my inexperience shows as
I do not have anything concrete to
> make that assumption) so I would really like to know why this is happening
and how to correct it.
> Thank you.
> gdr
> --
> Gary D. Rezek
> university Nerworking Systems and Services
> South Dakota State University
>
>|||Hi Andy,
Yes both boxes are on the same domain and have the same user accounts in the
m. As far as I can tell the 2 boxes
are near identical with their setups. The AD guys have set a lockout policy
of 5 bad logins within 15 minutes
locks the account out for 15 minutes.
Thanks.
gdr
"Andy Davis" <activecrypt@.gmail.com> wrote in message news:873FAFB3-F604-45F4-913F-EAF6D2C0A
CA0@.microsoft.com...[vbcol=seagreen]
> Hi,
> Is both SQL box on same Domain ? are they have the same User Account in it
?
> Have you set Password Policy for Account Lockout ?if so ,after how many
> attempts it locks account ? i suspect that theirs is no such user ..
> Regards
> --
> Andy Davis
> Active Crypt Team
> ---SQL Server Encryption
> Decryption Software
> http://www.activecrypt.com
>
> "Gary D. Rezek" wrote:
>
Sunday, March 11, 2012
could not locate entry in sysdatabases
Hey there, could someone please help me!!
I had created a database in sql server but since then installed windows xp pro and now when i go through the microsoft sql server dsn configuration the database is not valid and therefore i cannot change the default database as it says it doesn't exist.
So then when i type in command prompt use 'db' it says it doesn't exist but when i try to create 'db' it says that the database already exists.
I get the error message, could not locate entry in sysdatabases for 'cti' (database name).
When i look in mysql - data - along with master etc there is my cti.mdf and log files??
I'm stuck?
Is it that the files just aren't registering through sql server?
Please help!Have you tried using enterprise manager or query analyzer ? Also, can you be more specific when you say "installed windows xp pro". Which version of sql server are you using ? When you configure your dsn, what are you putting in the "Server" dropdown ? Have any of your security settings changed and which type of security are you using to access sql server ? Have you tried to create a new dsn ?|||Hey there, i use (local) for the server in the dsn configuration.
I have just put on windows xp pro sp1 - I orginally had an earlier windows xp pro.
I'm using sql server 2000 sp3
All security settings have remained the same and I've tried to do new dsn's but they still don't register that the database files aren't in the sysdatabases.
I had created a database in sql server but since then installed windows xp pro and now when i go through the microsoft sql server dsn configuration the database is not valid and therefore i cannot change the default database as it says it doesn't exist.
So then when i type in command prompt use 'db' it says it doesn't exist but when i try to create 'db' it says that the database already exists.
I get the error message, could not locate entry in sysdatabases for 'cti' (database name).
When i look in mysql - data - along with master etc there is my cti.mdf and log files??
I'm stuck?
Is it that the files just aren't registering through sql server?
Please help!Have you tried using enterprise manager or query analyzer ? Also, can you be more specific when you say "installed windows xp pro". Which version of sql server are you using ? When you configure your dsn, what are you putting in the "Server" dropdown ? Have any of your security settings changed and which type of security are you using to access sql server ? Have you tried to create a new dsn ?|||Hey there, i use (local) for the server in the dsn configuration.
I have just put on windows xp pro sp1 - I orginally had an earlier windows xp pro.
I'm using sql server 2000 sp3
All security settings have remained the same and I've tried to do new dsn's but they still don't register that the database files aren't in the sysdatabases.
Could not load type 'System.Data.SqlServerCe.SqlCeDataAdapter' from assembly 'System.Data.Sql
Hi,
I am trying to make a mobile application work, but I get the following error. The operating system on Pocket PC is Microsoft? Windows Mobile? 2003 Second Edition. Any ideas? Thanks in advance.
The followings are the error and my codes:
System.TypeLoadException was unhandled
Message="Could not load type 'System.Data.SqlServerCe.SqlCeDataAdapter' from assembly 'System.Data.SqlServerCe, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91'."
StackTrace:
at SQLMobile.Form1.Form1_Load()
at System.Windows.Forms.Form.OnLoad()
at System.Windows.Forms.Form._SetVisibleNotify()
at System.Windows.Forms.Control.set_Visible()
at System.Windows.Forms.Application.Run()
at SQLMobile.Form1.Main()
Codes:
Private Sub FillGrid()
Dim filename As New String _
("\Program Files\SQLMobile\sqlmobile.sdf")
Dim conn As New SqlCeConnection("Data Source=" + filename)
Dim selectCmd As SqlCeCommand = conn.CreateCommand()
selectCmd.CommandText = "select Destination from flightdata"
Dim adp As New SqlCeDataAdapter(selectCmd)
Dim ds As New DataSet()
adp.Fill(ds)
DataGrid1.DataSource = ds
End sub
First, make sure the version of the System.Data.SqlServerCe is the correct one for Compact Framework 2.0 (not the CF1 version which only works with SQL CE 2.0)
Next, uninstall then reinstall SQL Mobile CABs on your device.
Finally, don't use the SqlCeDataAdaper to populate that DataSet - it is the absolute slowest option! Use either the SqlCeDataReader or the SqlCeResultSet to do so.
Darren
Could not find xp_sqlagent_proxy_account
Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!
Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!
|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
[vbcol=seagreen]
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John
|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default...b;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
[vbcol=seagreen]
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default...b;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.
|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?
|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default...b;en-us;248391
http://support.microsoft.com/default...b;en-us;253107
John[vbcol=seagreen]
> Thanks again!
> "John Bell" wrote:
|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via droptable.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!
Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!
|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
[vbcol=seagreen]
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John
|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default...b;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
[vbcol=seagreen]
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default...b;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.
|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?
|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default...b;en-us;248391
http://support.microsoft.com/default...b;en-us;253107
John[vbcol=seagreen]
> Thanks again!
> "John Bell" wrote:
|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via droptable.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>
Could not find xp_sqlagent_proxy_account
Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
> > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > account. It says successfully, but I cannot find any local account
> > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > Have you tried changing this from the Services applet?
> >
> > John
> >
> > "Min" wrote:
> >
> > > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > > account. It says successfully, but I cannot find any local account
> > > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > I don't have a SQL 7 system to check, but the if you can't find the stored
> > procedure in the master database using Enterprise Manager, then it was either
> > deleted for security or does not exist in that version.
> >
> > The local users are accessed through the Server applet in control panel. The
> > services applet in control panel will allow you to select a different user
> > for the service to be run as.
> >
> > John|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
John
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> >
> > If the machine is NT workstation you can manage local users using
> > musrmgr.exe but this is not available on NT Server.
> >
> > What account is the service running under in the services applet? Usually
> > the account would be a domain user with restricted privileges.|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via SQLMonster.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>|||Thanks. I guess my question now is really:
How can I create a proxy account correctly? Thru EM, I unchecked the box,
clicked "reset ..." and message came back saying " successfully". But I am
still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
non-admin account.
Also, there is no utility on NT server to verify the account.
"John Bell" wrote:
> Hi
> See inline:
> "Min" wrote:
> > So is it right for SQL Server 7, the only way to reset proxy account is thru
> > EM, not programatically?
> Probably but I don't have a system to check this. There may be a way to
> write your own process to do this, but whether this is a justified effort for
> a version of the product that is so old, I don't know. You may want to trace
> what happens when you use EM and see what if you can do the same.
> >
> > Does it mean for NT Server, there is no way I can check to verify if the
> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
> > the "reset proxy" account button in "Job System", it says "successfully" but
> > there is an error log entry for agent says "SQLAgentCmdExec password
> > verification failed, required client privilege not held".
> Is there anything in the Event log?
> >
> > We use a domain acount for both SQL and Agent services. It is in local
> > administrator group.
> You may also want to check:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
> John
> >
> > Thanks again!
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> > >
> > > If the machine is NT workstation you can manage local users using
> > > musrmgr.exe but this is not available on NT Server.
> > >
> > > What account is the service running under in the services applet? Usually
> > > the account would be a domain user with restricted privileges.|||Yes...use Enterprise Manager and the Reset Proxy on the Job
System tab in SQL Agent Properties. Refer to the following
for more info:
INF: Reset Proxy and the SQLAgentCmdExec Account
http://support.microsoft.com/?id=264155
But your issues are likely related to the service account,
not the proxy account. In regards to the 1314 error, that's
generally related to rights of the MSSQLServer service
account, *not* the proxy account. So it's that account that
is missing the rights of either/both Act as part of
operating system and increase quotas. You could also be
missing Replace process level token based on some of what
you posted earlier. I'm pretty sure there is a Knowledge
base article on this somewhere.
Sounds like you have some issues with the MSSQLServer
service account and that you may have changed it through the
services applet instead of Enterprise Manager. If you change
the service account through Enterprise Manager, the
permissions and rights will be set correctly.
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Okay...and right after I posted, I found the other KB
article I mentioned that has more info on error 1314:
PRB: Error 1314 Raised By xp_cmdshell When Executed as
Non-SA User
http://support.microsoft.com/?id=248391
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Thanks ... I have tried to follow both articles (actually almost every
article online that I can dig out). It is still not working even though EM
says "successfully". I decided to use another technology instead of
XP_cmdshell. My guess is that some kind of security patches blocked it.
"Sue Hoegemeier" wrote:
> Okay...and right after I posted, I found the other KB
> article I mentioned that has more info on error 1314:
> PRB: Error 1314 Raised By xp_cmdshell When Executed as
> Non-SA User
> http://support.microsoft.com/?id=248391
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
> > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > account. It says successfully, but I cannot find any local account
> > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > Have you tried changing this from the Services applet?
> >
> > John
> >
> > "Min" wrote:
> >
> > > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > > account. It says successfully, but I cannot find any local account
> > > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > I don't have a SQL 7 system to check, but the if you can't find the stored
> > procedure in the master database using Enterprise Manager, then it was either
> > deleted for security or does not exist in that version.
> >
> > The local users are accessed through the Server applet in control panel. The
> > services applet in control panel will allow you to select a different user
> > for the service to be run as.
> >
> > John|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
John
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> >
> > If the machine is NT workstation you can manage local users using
> > musrmgr.exe but this is not available on NT Server.
> >
> > What account is the service running under in the services applet? Usually
> > the account would be a domain user with restricted privileges.|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via SQLMonster.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>|||Thanks. I guess my question now is really:
How can I create a proxy account correctly? Thru EM, I unchecked the box,
clicked "reset ..." and message came back saying " successfully". But I am
still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
non-admin account.
Also, there is no utility on NT server to verify the account.
"John Bell" wrote:
> Hi
> See inline:
> "Min" wrote:
> > So is it right for SQL Server 7, the only way to reset proxy account is thru
> > EM, not programatically?
> Probably but I don't have a system to check this. There may be a way to
> write your own process to do this, but whether this is a justified effort for
> a version of the product that is so old, I don't know. You may want to trace
> what happens when you use EM and see what if you can do the same.
> >
> > Does it mean for NT Server, there is no way I can check to verify if the
> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
> > the "reset proxy" account button in "Job System", it says "successfully" but
> > there is an error log entry for agent says "SQLAgentCmdExec password
> > verification failed, required client privilege not held".
> Is there anything in the Event log?
> >
> > We use a domain acount for both SQL and Agent services. It is in local
> > administrator group.
> You may also want to check:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
> John
> >
> > Thanks again!
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> > >
> > > If the machine is NT workstation you can manage local users using
> > > musrmgr.exe but this is not available on NT Server.
> > >
> > > What account is the service running under in the services applet? Usually
> > > the account would be a domain user with restricted privileges.|||Yes...use Enterprise Manager and the Reset Proxy on the Job
System tab in SQL Agent Properties. Refer to the following
for more info:
INF: Reset Proxy and the SQLAgentCmdExec Account
http://support.microsoft.com/?id=264155
But your issues are likely related to the service account,
not the proxy account. In regards to the 1314 error, that's
generally related to rights of the MSSQLServer service
account, *not* the proxy account. So it's that account that
is missing the rights of either/both Act as part of
operating system and increase quotas. You could also be
missing Replace process level token based on some of what
you posted earlier. I'm pretty sure there is a Knowledge
base article on this somewhere.
Sounds like you have some issues with the MSSQLServer
service account and that you may have changed it through the
services applet instead of Enterprise Manager. If you change
the service account through Enterprise Manager, the
permissions and rights will be set correctly.
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Okay...and right after I posted, I found the other KB
article I mentioned that has more info on error 1314:
PRB: Error 1314 Raised By xp_cmdshell When Executed as
Non-SA User
http://support.microsoft.com/?id=248391
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Thanks ... I have tried to follow both articles (actually almost every
article online that I can dig out). It is still not working even though EM
says "successfully". I decided to use another technology instead of
XP_cmdshell. My guess is that some kind of security patches blocked it.
"Sue Hoegemeier" wrote:
> Okay...and right after I posted, I found the other KB
> article I mentioned that has more info on error 1314:
> PRB: Error 1314 Raised By xp_cmdshell When Executed as
> Non-SA User
> http://support.microsoft.com/?id=248391
Could not find xp_sqlagent_proxy_account
Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
>|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was eithe
r
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
[vbcol=seagreen]
> When you say "change this", can you please explan what you are referring t
o?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
>|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find th
e
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was eit
her
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. T
he
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/defaul...kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
[vbcol=seagreen]
> 1. Could it be deleted by some service patches from EM? But I can still fi
nd
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot ha
ve
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find
the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
>|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/defaul...kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there
a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is th
ru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort fo
r
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clickin
g
> the "reset proxy" account button in "Job System", it says "successfully" b
ut
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/defaul...kb;en-us;248391
http://support.microsoft.com/defaul...kb;en-us;253107
John[vbcol=seagreen]
> Thanks again!
> "John Bell" wrote:
>|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via droptable.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is ther
e a
> way to get the syntax of these procedures and just create on of our own?
>
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
>|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was eithe
r
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
[vbcol=seagreen]
> When you say "change this", can you please explan what you are referring t
o?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
>|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find th
e
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was eit
her
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. T
he
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/defaul...kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
[vbcol=seagreen]
> 1. Could it be deleted by some service patches from EM? But I can still fi
nd
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot ha
ve
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find
the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
>|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/defaul...kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there
a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is th
ru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort fo
r
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clickin
g
> the "reset proxy" account button in "Job System", it says "successfully" b
ut
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/defaul...kb;en-us;248391
http://support.microsoft.com/defaul...kb;en-us;253107
John[vbcol=seagreen]
> Thanks again!
> "John Bell" wrote:
>|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via droptable.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is ther
e a
> way to get the syntax of these procedures and just create on of our own?
>
Wednesday, March 7, 2012
Could not find file 'C:\WINDOWS\TEMP\
When I try to connect to the reporting server using sql server management studio, I get the following error
TITLE: Connect to Server
Cannot connect to hq-v-w2k3-rpt0.
ADDITIONAL INFORMATION:
System.Web.Services.Protocols.SoapException: Server was unable to process request. > System.IO.FileNotFoundException: Could not find file 'C:\WINDOWS\TEMP\7cxlkihr.dll'.
File name: 'C:\WINDOWS\TEMP\7cxlkihr.dll'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, CompilerParameters parameters, Evidence evidence)
at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, CompilerParameters parameters, Assembly assembly, Hashtable assemblies)
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings, Evidence evidence)
at System.Web.Services.Protocols.SoapServerType..ctor(Type type, WebServiceProtocols protocolsSupported)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
End of inner exception stack trace (Microsoft.SqlServer.Management.UI.RSClient)
It was working until today. nothing changed except I got a microsoft update, could that have caused it?
Nevermind. There must have been something going on in my environment becuase I got another update Update for SQL Server 2005 (KB 932557) and now its fixed.
|||Hi,
Could you please five the complete url where we can get the this update please. Thanks in advance for you help.
Thanks & Regards,
Venkat.
Could not find file 'C:\WINDOWS\TEMP\
When I try to connect to the reporting server using sql server management studio, I get the following error
TITLE: Connect to Server
Cannot connect to hq-v-w2k3-rpt0.
ADDITIONAL INFORMATION:
System.Web.Services.Protocols.SoapException: Server was unable to process request. > System.IO.FileNotFoundException: Could not find file 'C:\WINDOWS\TEMP\7cxlkihr.dll'.
File name: 'C:\WINDOWS\TEMP\7cxlkihr.dll'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, CompilerParameters parameters, Evidence evidence)
at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, CompilerParameters parameters, Assembly assembly, Hashtable assemblies)
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings, Evidence evidence)
at System.Web.Services.Protocols.SoapServerType..ctor(Type type, WebServiceProtocols protocolsSupported)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
End of inner exception stack trace (Microsoft.SqlServer.Management.UI.RSClient)
It was working until today. nothing changed except I got a microsoft update, could that have caused it?
Nevermind. There must have been something going on in my environment becuase I got another update Update for SQL Server 2005 (KB 932557) and now its fixed.
|||Hi,
Could you please five the complete url where we can get the this update please. Thanks in advance for you help.
Thanks & Regards,
Venkat.
Could not find file 'C:\WINDOWS\system32\dbo.mdb
Error message "OLE DB error: OLE DB or ODBC error: Could not find file 'C:\WINDOWS\system32\dbo.mdb'.; 3024. is reported when I try to process a cube in the SQL Server Management Studio and in the SQL Server Business Intelligence Development Studio.
What is the problem, I didn't install new software!!
Check the data source connection string. It looks like a Jet data source pointing to C:\WINDOWS\system32\dbo.mdb. Edit the data source in SQL Mgmt Studio and fix it.
|||This is not a data source connection problem, all the cubes are reporting the same error message!!|||If Analysis Services is raising this error, then this Jet connection string must be specified *somewhere*. Check the config file msmdsrv.ini (or server properties in mgmt studio). Maybe the query log or something else points to this mdb.|||This error message do not appear when I'm connected to the network, only when I work stand alone!!!
My connection string in the data source property window:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Data\SQL2005Cubes\TBC_Europe.mdb
Saturday, February 25, 2012
Could not establish trust relationship with remote server.
I am trying to setup SQL Server 2000 Reporting services with an SSL
connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
have tried setting up Certificates from both and Stand-Alone and Enterprise
CA. I have tried several combinations of the Issue To name (server |
server.company | server.company.local) I have modified the
rsWebApplication.config and rsReportServer.config to match the certificateâ's
Issue to exactly. I have tried installs with both Domain Accounts and NT
AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
to work but I have had no luck with the report manager
https://server/reports. How do I fix this error?
ThankyouThe most likely reason this is failing is that your Report Server does not
trust the Root Certificate Authority that created the certificate you are
using.
If you go to https://machine/ReportServer and IE says "this certificate is
not valid are you sure you want to accept it?" then you will know that the
certificate is not 100% trusted and that is why you are receiving the error.
You will need to export the Trusted Root Authority certificate from the
issuing server and import it on the Report Server.
--
SQL Server Developer Support Engineer
"vbchewie" wrote:
> I am trying to setup SQL Server 2000 Reporting services with an SSL
> connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> have tried setting up Certificates from both and Stand-Alone and Enterprise
> CA. I have tried several combinations of the Issue To name (server |
> server.company | server.company.local) I have modified the
> rsWebApplication.config and rsReportServer.config to match the certificateâ's
> Issue to exactly. I have tried installs with both Domain Accounts and NT
> AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> to work but I have had no luck with the report manager
> https://server/reports. How do I fix this error?
> Thankyou
>|||I went to the stand alone root certificate authority and exported the
certificate for that server. I then imported it into both the SQL Server and
Reporting Server. Now when I type the FQDN
(https://machine.domain.local/Reports ) I no longer get a certificate error,
but I do still get â'The underlying connection was closed: Could not establish
trust relationship with remote server.â'
Is there something else I can do? Does it have to be an Enterprise Root
Certificate Authority in order to work?
Thank You.
"Chris Alton [MS]" wrote:
> The most likely reason this is failing is that your Report Server does not
> trust the Root Certificate Authority that created the certificate you are
> using.
> If you go to https://machine/ReportServer and IE says "this certificate is
> not valid are you sure you want to accept it?" then you will know that the
> certificate is not 100% trusted and that is why you are receiving the error.
> You will need to export the Trusted Root Authority certificate from the
> issuing server and import it on the Report Server.
> --
> SQL Server Developer Support Engineer
>
> "vbchewie" wrote:
> > I am trying to setup SQL Server 2000 Reporting services with an SSL
> > connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> > Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> > have tried setting up Certificates from both and Stand-Alone and Enterprise
> > CA. I have tried several combinations of the Issue To name (server |
> > server.company | server.company.local) I have modified the
> > rsWebApplication.config and rsReportServer.config to match the certificateâ's
> > Issue to exactly. I have tried installs with both Domain Accounts and NT
> > AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> > to work but I have had no luck with the report manager
> > https://server/reports. How do I fix this error?
> >
> > Thankyou
> >|||You also need to make sure that the SSL certificate you are using matches
the machine name you are accessing it by EXACTLY. You will also need to
make sure that in the Reporting Services configuration tool that you have
checked the "Require Secure Socket Layer (SSL) Connections" and put the
same name you are accessing the server by in the "Certificate Name" field.
So in your example you would put "machine.domain.local" in the Certificate
Field and the certificate should be issued to "machine.domain.local".
The easiest way to tell if the certificate is valid is to open up
https://machine.domain.local/ReportServer from the web server and if IE
complains about the certificate at all then it will not work.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||In RSReportServer.config I have my "SecureConnectionLevel" Value="3" and my
<UrlRoot>https://machine.domain.local/ReportServer</UrlRoot>
in RSWebApplication.config
I have
<ReportServerUrl>https://machine.domain.local/ReportServer</ReportServerUrl>
When I go to IIS on the Reporting Server and right click on Default Web Site
> Properties > Directory Security.
And click on 'View Certificate...' it says Issued to: machine.domain.local I
also checked the friendly name it also has machine.domain.local.
When I click 'Edit...' under 'Secure communications' both Require secure
channel(SSL) and Require 128-bit encryption are checked.
When I click 'Edit...' Under 'Authentication and access control' Enable
anonymous access is unchecked.
The same is true for my Virtual Directories 'Reports' and ReportServer'
When I go to https://machine/domain.local/Reports there are no certificate
errors. It goes straight though to a page that says
"The underlying connection was closed: Could not establish trust
relationship with remote server."
You mentioned Reporting Services Configuration Tool. This is Reporting
Services for SQL Server 2000. Is there a Reporting Services Configuration
Tool for this version? I thought that was for 2005.
Iâ'm not sure what I am missing. Any other ideas?
Thank you
"Chris Alton [MSFT]" wrote:
> You also need to make sure that the SSL certificate you are using matches
> the machine name you are accessing it by EXACTLY. You will also need to
> make sure that in the Reporting Services configuration tool that you have
> checked the "Require Secure Socket Layer (SSL) Connections" and put the
> same name you are accessing the server by in the "Certificate Name" field.
> So in your example you would put "machine.domain.local" in the Certificate
> Field and the certificate should be issued to "machine.domain.local".
> The easiest way to tell if the certificate is valid is to open up
> https://machine.domain.local/ReportServer from the web server and if IE
> complains about the certificate at all then it will not work.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||I didn't know you were using SQL 2000. The only thing I can think of is
that you need to install the Root CA Certificate in the Certificate Store
of the Machine account. What account do you have the SRS Windows Service
and the IIS Application Pool running under?
If it is LocalSystem or Network Service you can install the certificate by
following these steps:
a. Click Start->Run
b. Type mmc and hit enter.
c. Click File->Add/Remove Snap-in
d. Click the "Add" button.
e. Select "Certificates" from the list
f. Click the "Add" button.
g. Click the "Computer Account" radio button.
h. Click "Next"
i. Make sure "Local Computer" is selected and click "Finish"
j. Click "Close"
k. Click "Ok"
l. Branch down on Certificates.
m. Right click Trusted Root Certification Authorities->All
Tasks->Import...
n. Click "Next" and browse to the certificate you are importing.
o. Click "Next" and make sure the "Place all certificates in the
following store" is selected and "Trusted Root Certification Authorities"
is listed in the "Certificate Store" box. If not browse to it by clicking
the "Browse" button.
p. Click "Next" and then click "Finish"
q. The Trusted Root Authority Certificate should now be imported and
available to web application/service.
Hopefully that should get it now.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||It works!!!
SRS is running under a domain\account. In order to get Kerberos to function
properly I used setspn to allow the domain\account to use the http service.
So I am not running under LocalSystem or Network Service.
I logged into the computer with the domain\account that is running both the
SRS Service and the ReportingServices Application Pool. I followed your
directions exactly with only one variation. Instead of picking "Computer
Account" at g. I chose "My Account". It looks like it is working now.
To recap for anyone else that runs into this issue:
SQL Server 2000 is on machine1
SharePoint and Reporting Services are on machine2 and are running under a
domain\account (very limited rights).
SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
Thank you very much for your help,
"Chris Alton [MSFT]" wrote:
> I didn't know you were using SQL 2000. The only thing I can think of is
> that you need to install the Root CA Certificate in the Certificate Store
> of the Machine account. What account do you have the SRS Windows Service
> and the IIS Application Pool running under?
> If it is LocalSystem or Network Service you can install the certificate by
> following these steps:
> a. Click Start->Run
> b. Type mmc and hit enter.
> c. Click File->Add/Remove Snap-in
> d. Click the "Add" button.
> e. Select "Certificates" from the list
> f. Click the "Add" button.
> g. Click the "Computer Account" radio button.
> h. Click "Next"
> i. Make sure "Local Computer" is selected and click "Finish"
> j. Click "Close"
> k. Click "Ok"
> l. Branch down on Certificates.
> m. Right click Trusted Root Certification Authorities->All
> Tasks->Import...
> n. Click "Next" and browse to the certificate you are importing.
> o. Click "Next" and make sure the "Place all certificates in the
> following store" is selected and "Trusted Root Certification Authorities"
> is listed in the "Certificate Store" box. If not browse to it by clicking
> the "Browse" button.
> p. Click "Next" and then click "Finish"
> q. The Trusted Root Authority Certificate should now be imported and
> available to web application/service.
> Hopefully that should get it now.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||If the Windows Service and Application Pool all run under a domain account
then you really don't have to go through all those convoluted steps to
import the cert. That is only if you are using LocalSystem/Network Service
since those are considered the "Machine" account.
If you can log on to the account in an interactive session all you really
have to do to import the certificate is logon and then double click the
cer file and follow the prompts :)
Glad its working for you now though, those SSL issues with SRS can be quite
complicated sometimes.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Could not establish trust relationship with remote server.
> From: <vbchewie@.discussions.microsoft.com>
> Subject: RE: Could not establish trust relationship with remote server.
> Date: Tue, 2 Oct 2007 14:18:01 -0700
> It works!!!
> SRS is running under a domain\account. In order to get Kerberos to
function
> properly I used setspn to allow the domain\account to use the http
service.
> So I am not running under LocalSystem or Network Service.
> I logged into the computer with the domain\account that is running both
the
> SRS Service and the ReportingServices Application Pool. I followed your
> directions exactly with only one variation. Instead of picking "Computer
> Account" at g. I chose "My Account". It looks like it is working now.
> To recap for anyone else that runs into this issue:
> SQL Server 2000 is on machine1
> SharePoint and Reporting Services are on machine2 and are running under a
> domain\account (very limited rights).
> SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
> Thank you very much for your help,
>
> "Chris Alton [MSFT]" wrote:
> > I didn't know you were using SQL 2000. The only thing I can think of is
> > that you need to install the Root CA Certificate in the Certificate
Store
> > of the Machine account. What account do you have the SRS Windows
Service
> > and the IIS Application Pool running under?
> >
> > If it is LocalSystem or Network Service you can install the certificate
by
> > following these steps:
> >
> > a. Click Start->Run
> > b. Type mmc and hit enter.
> > c. Click File->Add/Remove Snap-in
> > d. Click the "Add" button.
> > e. Select "Certificates" from the list
> > f. Click the "Add" button.
> > g. Click the "Computer Account" radio button.
> > h. Click "Next"
> > i. Make sure "Local Computer" is selected and click "Finish"
> > j. Click "Close"
> > k. Click "Ok"
> > l. Branch down on Certificates.
> > m. Right click Trusted Root Certification Authorities->All
> > Tasks->Import...
> > n. Click "Next" and browse to the certificate you are importing.
> > o. Click "Next" and make sure the "Place all certificates in the
> > following store" is selected and "Trusted Root Certification
Authorities"
> > is listed in the "Certificate Store" box. If not browse to it by
clicking
> > the "Browse" button.
> > p. Click "Next" and then click "Finish"
> > q. The Trusted Root Authority Certificate should now be imported
and
> > available to web application/service.
> >
> > Hopefully that should get it now.
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
>
connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
have tried setting up Certificates from both and Stand-Alone and Enterprise
CA. I have tried several combinations of the Issue To name (server |
server.company | server.company.local) I have modified the
rsWebApplication.config and rsReportServer.config to match the certificateâ's
Issue to exactly. I have tried installs with both Domain Accounts and NT
AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
to work but I have had no luck with the report manager
https://server/reports. How do I fix this error?
ThankyouThe most likely reason this is failing is that your Report Server does not
trust the Root Certificate Authority that created the certificate you are
using.
If you go to https://machine/ReportServer and IE says "this certificate is
not valid are you sure you want to accept it?" then you will know that the
certificate is not 100% trusted and that is why you are receiving the error.
You will need to export the Trusted Root Authority certificate from the
issuing server and import it on the Report Server.
--
SQL Server Developer Support Engineer
"vbchewie" wrote:
> I am trying to setup SQL Server 2000 Reporting services with an SSL
> connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> have tried setting up Certificates from both and Stand-Alone and Enterprise
> CA. I have tried several combinations of the Issue To name (server |
> server.company | server.company.local) I have modified the
> rsWebApplication.config and rsReportServer.config to match the certificateâ's
> Issue to exactly. I have tried installs with both Domain Accounts and NT
> AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> to work but I have had no luck with the report manager
> https://server/reports. How do I fix this error?
> Thankyou
>|||I went to the stand alone root certificate authority and exported the
certificate for that server. I then imported it into both the SQL Server and
Reporting Server. Now when I type the FQDN
(https://machine.domain.local/Reports ) I no longer get a certificate error,
but I do still get â'The underlying connection was closed: Could not establish
trust relationship with remote server.â'
Is there something else I can do? Does it have to be an Enterprise Root
Certificate Authority in order to work?
Thank You.
"Chris Alton [MS]" wrote:
> The most likely reason this is failing is that your Report Server does not
> trust the Root Certificate Authority that created the certificate you are
> using.
> If you go to https://machine/ReportServer and IE says "this certificate is
> not valid are you sure you want to accept it?" then you will know that the
> certificate is not 100% trusted and that is why you are receiving the error.
> You will need to export the Trusted Root Authority certificate from the
> issuing server and import it on the Report Server.
> --
> SQL Server Developer Support Engineer
>
> "vbchewie" wrote:
> > I am trying to setup SQL Server 2000 Reporting services with an SSL
> > connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> > Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> > have tried setting up Certificates from both and Stand-Alone and Enterprise
> > CA. I have tried several combinations of the Issue To name (server |
> > server.company | server.company.local) I have modified the
> > rsWebApplication.config and rsReportServer.config to match the certificateâ's
> > Issue to exactly. I have tried installs with both Domain Accounts and NT
> > AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> > to work but I have had no luck with the report manager
> > https://server/reports. How do I fix this error?
> >
> > Thankyou
> >|||You also need to make sure that the SSL certificate you are using matches
the machine name you are accessing it by EXACTLY. You will also need to
make sure that in the Reporting Services configuration tool that you have
checked the "Require Secure Socket Layer (SSL) Connections" and put the
same name you are accessing the server by in the "Certificate Name" field.
So in your example you would put "machine.domain.local" in the Certificate
Field and the certificate should be issued to "machine.domain.local".
The easiest way to tell if the certificate is valid is to open up
https://machine.domain.local/ReportServer from the web server and if IE
complains about the certificate at all then it will not work.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||In RSReportServer.config I have my "SecureConnectionLevel" Value="3" and my
<UrlRoot>https://machine.domain.local/ReportServer</UrlRoot>
in RSWebApplication.config
I have
<ReportServerUrl>https://machine.domain.local/ReportServer</ReportServerUrl>
When I go to IIS on the Reporting Server and right click on Default Web Site
> Properties > Directory Security.
And click on 'View Certificate...' it says Issued to: machine.domain.local I
also checked the friendly name it also has machine.domain.local.
When I click 'Edit...' under 'Secure communications' both Require secure
channel(SSL) and Require 128-bit encryption are checked.
When I click 'Edit...' Under 'Authentication and access control' Enable
anonymous access is unchecked.
The same is true for my Virtual Directories 'Reports' and ReportServer'
When I go to https://machine/domain.local/Reports there are no certificate
errors. It goes straight though to a page that says
"The underlying connection was closed: Could not establish trust
relationship with remote server."
You mentioned Reporting Services Configuration Tool. This is Reporting
Services for SQL Server 2000. Is there a Reporting Services Configuration
Tool for this version? I thought that was for 2005.
Iâ'm not sure what I am missing. Any other ideas?
Thank you
"Chris Alton [MSFT]" wrote:
> You also need to make sure that the SSL certificate you are using matches
> the machine name you are accessing it by EXACTLY. You will also need to
> make sure that in the Reporting Services configuration tool that you have
> checked the "Require Secure Socket Layer (SSL) Connections" and put the
> same name you are accessing the server by in the "Certificate Name" field.
> So in your example you would put "machine.domain.local" in the Certificate
> Field and the certificate should be issued to "machine.domain.local".
> The easiest way to tell if the certificate is valid is to open up
> https://machine.domain.local/ReportServer from the web server and if IE
> complains about the certificate at all then it will not work.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||I didn't know you were using SQL 2000. The only thing I can think of is
that you need to install the Root CA Certificate in the Certificate Store
of the Machine account. What account do you have the SRS Windows Service
and the IIS Application Pool running under?
If it is LocalSystem or Network Service you can install the certificate by
following these steps:
a. Click Start->Run
b. Type mmc and hit enter.
c. Click File->Add/Remove Snap-in
d. Click the "Add" button.
e. Select "Certificates" from the list
f. Click the "Add" button.
g. Click the "Computer Account" radio button.
h. Click "Next"
i. Make sure "Local Computer" is selected and click "Finish"
j. Click "Close"
k. Click "Ok"
l. Branch down on Certificates.
m. Right click Trusted Root Certification Authorities->All
Tasks->Import...
n. Click "Next" and browse to the certificate you are importing.
o. Click "Next" and make sure the "Place all certificates in the
following store" is selected and "Trusted Root Certification Authorities"
is listed in the "Certificate Store" box. If not browse to it by clicking
the "Browse" button.
p. Click "Next" and then click "Finish"
q. The Trusted Root Authority Certificate should now be imported and
available to web application/service.
Hopefully that should get it now.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||It works!!!
SRS is running under a domain\account. In order to get Kerberos to function
properly I used setspn to allow the domain\account to use the http service.
So I am not running under LocalSystem or Network Service.
I logged into the computer with the domain\account that is running both the
SRS Service and the ReportingServices Application Pool. I followed your
directions exactly with only one variation. Instead of picking "Computer
Account" at g. I chose "My Account". It looks like it is working now.
To recap for anyone else that runs into this issue:
SQL Server 2000 is on machine1
SharePoint and Reporting Services are on machine2 and are running under a
domain\account (very limited rights).
SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
Thank you very much for your help,
"Chris Alton [MSFT]" wrote:
> I didn't know you were using SQL 2000. The only thing I can think of is
> that you need to install the Root CA Certificate in the Certificate Store
> of the Machine account. What account do you have the SRS Windows Service
> and the IIS Application Pool running under?
> If it is LocalSystem or Network Service you can install the certificate by
> following these steps:
> a. Click Start->Run
> b. Type mmc and hit enter.
> c. Click File->Add/Remove Snap-in
> d. Click the "Add" button.
> e. Select "Certificates" from the list
> f. Click the "Add" button.
> g. Click the "Computer Account" radio button.
> h. Click "Next"
> i. Make sure "Local Computer" is selected and click "Finish"
> j. Click "Close"
> k. Click "Ok"
> l. Branch down on Certificates.
> m. Right click Trusted Root Certification Authorities->All
> Tasks->Import...
> n. Click "Next" and browse to the certificate you are importing.
> o. Click "Next" and make sure the "Place all certificates in the
> following store" is selected and "Trusted Root Certification Authorities"
> is listed in the "Certificate Store" box. If not browse to it by clicking
> the "Browse" button.
> p. Click "Next" and then click "Finish"
> q. The Trusted Root Authority Certificate should now be imported and
> available to web application/service.
> Hopefully that should get it now.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||If the Windows Service and Application Pool all run under a domain account
then you really don't have to go through all those convoluted steps to
import the cert. That is only if you are using LocalSystem/Network Service
since those are considered the "Machine" account.
If you can log on to the account in an interactive session all you really
have to do to import the certificate is logon and then double click the
cer file and follow the prompts :)
Glad its working for you now though, those SSL issues with SRS can be quite
complicated sometimes.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Could not establish trust relationship with remote server.
> From: <vbchewie@.discussions.microsoft.com>
> Subject: RE: Could not establish trust relationship with remote server.
> Date: Tue, 2 Oct 2007 14:18:01 -0700
> It works!!!
> SRS is running under a domain\account. In order to get Kerberos to
function
> properly I used setspn to allow the domain\account to use the http
service.
> So I am not running under LocalSystem or Network Service.
> I logged into the computer with the domain\account that is running both
the
> SRS Service and the ReportingServices Application Pool. I followed your
> directions exactly with only one variation. Instead of picking "Computer
> Account" at g. I chose "My Account". It looks like it is working now.
> To recap for anyone else that runs into this issue:
> SQL Server 2000 is on machine1
> SharePoint and Reporting Services are on machine2 and are running under a
> domain\account (very limited rights).
> SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
> Thank you very much for your help,
>
> "Chris Alton [MSFT]" wrote:
> > I didn't know you were using SQL 2000. The only thing I can think of is
> > that you need to install the Root CA Certificate in the Certificate
Store
> > of the Machine account. What account do you have the SRS Windows
Service
> > and the IIS Application Pool running under?
> >
> > If it is LocalSystem or Network Service you can install the certificate
by
> > following these steps:
> >
> > a. Click Start->Run
> > b. Type mmc and hit enter.
> > c. Click File->Add/Remove Snap-in
> > d. Click the "Add" button.
> > e. Select "Certificates" from the list
> > f. Click the "Add" button.
> > g. Click the "Computer Account" radio button.
> > h. Click "Next"
> > i. Make sure "Local Computer" is selected and click "Finish"
> > j. Click "Close"
> > k. Click "Ok"
> > l. Branch down on Certificates.
> > m. Right click Trusted Root Certification Authorities->All
> > Tasks->Import...
> > n. Click "Next" and browse to the certificate you are importing.
> > o. Click "Next" and make sure the "Place all certificates in the
> > following store" is selected and "Trusted Root Certification
Authorities"
> > is listed in the "Certificate Store" box. If not browse to it by
clicking
> > the "Browse" button.
> > p. Click "Next" and then click "Finish"
> > q. The Trusted Root Authority Certificate should now be imported
and
> > available to web application/service.
> >
> > Hopefully that should get it now.
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
>
Could not establish secure channel for SSL/TLS.
Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
The //localhost/reportserver give's me XXX/ReportServer - /
----
Microsoft SQL Server Reporting Services Version 8.00.1038.00
But when connecting to //localhost/reports i get the followwing error.
"
The underlying connection was closed: Could not establish secure channel for
SSL/TLS."
Never installed ssl, and have tried all the security and other ideas so far.
Can anyone help.
Thanks
JohnJohn wrote:
> Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
> The //localhost/reportserver give's me XXX/ReportServer - /
> ----
> Microsoft SQL Server Reporting Services Version 8.00.1038.00
> But when connecting to //localhost/reports i get the followwing error.
> "
> The underlying connection was closed: Could not establish secure channel for
> SSL/TLS."
> Never installed ssl, and have tried all the security and other ideas so far.
> Can anyone help.
> Thanks
> John
>
if you have certificate from root,then you have to start trusting it
with you server too :)
try to install it under trusted root certification authorities.|||did you find a solution for this issue?
Grego
From http://www.developmentnow.com/g/115_2005_10_0_0_626044/Could-not-establish-secure-channel-for-SSLTLS-.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com
The //localhost/reportserver give's me XXX/ReportServer - /
----
Microsoft SQL Server Reporting Services Version 8.00.1038.00
But when connecting to //localhost/reports i get the followwing error.
"
The underlying connection was closed: Could not establish secure channel for
SSL/TLS."
Never installed ssl, and have tried all the security and other ideas so far.
Can anyone help.
Thanks
JohnJohn wrote:
> Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
> The //localhost/reportserver give's me XXX/ReportServer - /
> ----
> Microsoft SQL Server Reporting Services Version 8.00.1038.00
> But when connecting to //localhost/reports i get the followwing error.
> "
> The underlying connection was closed: Could not establish secure channel for
> SSL/TLS."
> Never installed ssl, and have tried all the security and other ideas so far.
> Can anyone help.
> Thanks
> John
>
if you have certificate from root,then you have to start trusting it
with you server too :)
try to install it under trusted root certification authorities.|||did you find a solution for this issue?
Grego
From http://www.developmentnow.com/g/115_2005_10_0_0_626044/Could-not-establish-secure-channel-for-SSLTLS-.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com
Could not Create Publication
Hi,
I created 2 windows user named PublishUser and ReplSnapAgent with less
previllege. Ran SSMS using PublishUser and created snapshot publication.
Used RepSnapAgent user as Snapshot Agent. I got an error saying
SQL Server could not create publication 'Product'. (New Publication Wizard)
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
Proxy "Computer-Name\ReplSnapAgent" is not a valid Windows user.
Changed database context to 'ReplTesting'. (.Net SqlClient Data Provider)
Is anybody else help me out in solving this issue?
Is ReplSnapAgent a local user account on the computer Computer-Name? Is it
in the dbo_role on the distribution database and the publication?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bharathi" <NoSpam_BB@.hotmail.com> wrote in message
news:Of7JjnPKHHA.2632@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I created 2 windows user named PublishUser and ReplSnapAgent with less
> previllege. Ran SSMS using PublishUser and created snapshot publication.
> Used RepSnapAgent user as Snapshot Agent. I got an error saying
> SQL Server could not create publication 'Product'. (New Publication
> Wizard)
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> Proxy "Computer-Name\ReplSnapAgent" is not a valid Windows user.
> Changed database context to 'ReplTesting'. (.Net SqlClient Data Provider)
> Is anybody else help me out in solving this issue?
>
I created 2 windows user named PublishUser and ReplSnapAgent with less
previllege. Ran SSMS using PublishUser and created snapshot publication.
Used RepSnapAgent user as Snapshot Agent. I got an error saying
SQL Server could not create publication 'Product'. (New Publication Wizard)
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
Proxy "Computer-Name\ReplSnapAgent" is not a valid Windows user.
Changed database context to 'ReplTesting'. (.Net SqlClient Data Provider)
Is anybody else help me out in solving this issue?
Is ReplSnapAgent a local user account on the computer Computer-Name? Is it
in the dbo_role on the distribution database and the publication?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bharathi" <NoSpam_BB@.hotmail.com> wrote in message
news:Of7JjnPKHHA.2632@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I created 2 windows user named PublishUser and ReplSnapAgent with less
> previllege. Ran SSMS using PublishUser and created snapshot publication.
> Used RepSnapAgent user as Snapshot Agent. I got an error saying
> SQL Server could not create publication 'Product'. (New Publication
> Wizard)
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> Proxy "Computer-Name\ReplSnapAgent" is not a valid Windows user.
> Changed database context to 'ReplTesting'. (.Net SqlClient Data Provider)
> Is anybody else help me out in solving this issue?
>
Sunday, February 19, 2012
Could no longer login into SQL Express 2005
Hi All,
I have this weird problem and hope someone can help me.
I have a SQL Express 2005 installed in a Windows 2000 server. After the
initial installation, I can login into the SQL server using the SQL
2005 console. However suddenly, I no longer can login either using SA
or Windows Authentication after a server reboot. I have enabled TCP/IP
and Named Pipes in the Network configuration.
The error message is,
TITLE: Connect to Server
--
Cannot connect to servername\MERCURY.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
BUTTONS:
OK
--
So now I am stuck. Is there anyway I can login or reset the password
for sa?
Thanks in advance.This is a very general message that the application can't find the SQL
Server. The most likely cause on a reboot, is that SQL Server was not
configured to start automatically, so you must start SQL Server. Use the SQL
Server Configuration Manager to do that.
Other common reasons are:
- Typed the name and instance wrong.
- You are connecting from another computer and the firewall is blocking you.
--
Rick Byham, MS
This posting is provided "AS IS" with no warranties, and confers no rights.
"mousehunt" <mousehunt@.gmail.com> wrote in message
news:1153043598.176242.291440@.m79g2000cwm.googlegroups.com...
> Hi All,
> I have this weird problem and hope someone can help me.
> I have a SQL Express 2005 installed in a Windows 2000 server. After the
> initial installation, I can login into the SQL server using the SQL
> 2005 console. However suddenly, I no longer can login either using SA
> or Windows Authentication after a server reboot. I have enabled TCP/IP
> and Named Pipes in the Network configuration.
> The error message is,
> TITLE: Connect to Server
> --
> Cannot connect to servername\MERCURY.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
> So now I am stuck. Is there anyway I can login or reset the password
> for sa?
> Thanks in advance.
>
I have this weird problem and hope someone can help me.
I have a SQL Express 2005 installed in a Windows 2000 server. After the
initial installation, I can login into the SQL server using the SQL
2005 console. However suddenly, I no longer can login either using SA
or Windows Authentication after a server reboot. I have enabled TCP/IP
and Named Pipes in the Network configuration.
The error message is,
TITLE: Connect to Server
--
Cannot connect to servername\MERCURY.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
BUTTONS:
OK
--
So now I am stuck. Is there anyway I can login or reset the password
for sa?
Thanks in advance.This is a very general message that the application can't find the SQL
Server. The most likely cause on a reboot, is that SQL Server was not
configured to start automatically, so you must start SQL Server. Use the SQL
Server Configuration Manager to do that.
Other common reasons are:
- Typed the name and instance wrong.
- You are connecting from another computer and the firewall is blocking you.
--
Rick Byham, MS
This posting is provided "AS IS" with no warranties, and confers no rights.
"mousehunt" <mousehunt@.gmail.com> wrote in message
news:1153043598.176242.291440@.m79g2000cwm.googlegroups.com...
> Hi All,
> I have this weird problem and hope someone can help me.
> I have a SQL Express 2005 installed in a Windows 2000 server. After the
> initial installation, I can login into the SQL server using the SQL
> 2005 console. However suddenly, I no longer can login either using SA
> or Windows Authentication after a server reboot. I have enabled TCP/IP
> and Named Pipes in the Network configuration.
> The error message is,
> TITLE: Connect to Server
> --
> Cannot connect to servername\MERCURY.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
> So now I am stuck. Is there anyway I can login or reset the password
> for sa?
> Thanks in advance.
>
Could I Install SP1 on windows xp
I have sql server 2005 standard edition.I have downloaded sp1 but can't able to install.I want's to know could i install it on windows xp.as on the page of sp1 i have read that it is for longhorn and vista.
I have the problem of creating diagram of my db.When i run
ALTER AUTHORIZATION ON DATABASE::pubs TO [kamranshahid\yukon]
it gives me the error.
Cannot find the principal 'kamranshahid\yukon', because it does not exist or you do not have permission.
I can't able to resolve it by command.I can't able to install sp1.What else can i do should I trash my sql server 2005 standard edition.
It seems you have 2 problems;
1/ Can't install SP1 of SQL Server 2005 on a copy of Std running on Win XP, correct? If so whats the error?
2/ You can't create diagrams on your RTM instance, correct? is 'kamranshahid\yukon' a user in the database? what perms does it have? what user are you logged in as an what perms do you have?
Subscribe to:
Posts (Atom)