SQL 2005 SP2 on Windows Server 2003 SP2
SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
32-bit. All use 32-bit SQL 2000.
Trying to create an Alias on a SQL 2000 machine to point to a named instance
on a SQL 2005 machine through TCP/IP (for use in replication).
When the alias is created on those SQL 2000 servers running a 32-bit OS, it
works.
When the alias is created on those SQL 2000 servers running a 64-bit OS, it
doesn't.
Instead, when I try to test using isql, I get:
DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
Una
ble to connect: SQL Server does not exist or network access denied.
Net-Library error 53: ConnectionOpen (Connect()).
Any ideas?
Thanks,
Tim C
There seems to be a subtle incompatibility issue. We have started moving our
SQL 2000 servers to 32-bit OS's on virtual machines to avoid the issue.
But if anyone knows of a simpler fix we could implement, I would love to
hear it.
Thanks,
Tim C
"Tim C" wrote:
> SQL 2005 SP2 on Windows Server 2003 SP2
> SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
> Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
> 32-bit. All use 32-bit SQL 2000.
> Trying to create an Alias on a SQL 2000 machine to point to a named instance
> on a SQL 2005 machine through TCP/IP (for use in replication).
> When the alias is created on those SQL 2000 servers running a 32-bit OS, it
> works.
> When the alias is created on those SQL 2000 servers running a 64-bit OS, it
> doesn't.
> Instead, when I try to test using isql, I get:
> DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
> Una
> ble to connect: SQL Server does not exist or network access denied.
> Net-Library error 53: ConnectionOpen (Connect()).
> Any ideas?
> Thanks,
> Tim C
Showing posts with label machines. Show all posts
Showing posts with label machines. Show all posts
Tuesday, March 27, 2012
Alias not working on some machines
SQL 2005 SP2 on Windows Server 2003 SP2
SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
32-bit. All use 32-bit SQL 2000.
Trying to create an Alias on a SQL 2000 machine to point to a named instance
on a SQL 2005 machine through TCP/IP (for use in replication).
When the alias is created on those SQL 2000 servers running a 32-bit OS, it
works.
When the alias is created on those SQL 2000 servers running a 64-bit OS, it
doesn't.
Instead, when I try to test using isql, I get:
DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
Una
ble to connect: SQL Server does not exist or network access denied.
Net-Library error 53: ConnectionOpen (Connect()).
Any ideas?
Thanks,
Tim CThere seems to be a subtle incompatibility issue. We have started moving our
SQL 2000 servers to 32-bit OS's on virtual machines to avoid the issue.
But if anyone knows of a simpler fix we could implement, I would love to
hear it.
Thanks,
Tim C
"Tim C" wrote:
> SQL 2005 SP2 on Windows Server 2003 SP2
> SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
> Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
> 32-bit. All use 32-bit SQL 2000.
> Trying to create an Alias on a SQL 2000 machine to point to a named instance
> on a SQL 2005 machine through TCP/IP (for use in replication).
> When the alias is created on those SQL 2000 servers running a 32-bit OS, it
> works.
> When the alias is created on those SQL 2000 servers running a 64-bit OS, it
> doesn't.
> Instead, when I try to test using isql, I get:
> DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
> Una
> ble to connect: SQL Server does not exist or network access denied.
> Net-Library error 53: ConnectionOpen (Connect()).
> Any ideas?
> Thanks,
> Tim C|||I recently had a discussion in .tools about this. Paul O'kasick was nice enough to share his
findings. Aparently there's both a 32 and a 64 bit version of cliconfg.exe and these modify
different registry keys. Here's a quote from Paul most recent reply:
"The alias is working on our test machine. It turns out there is a 64 bit
version of cliconfg.exe (C:\WINDOWS\SysWOW64\cliconfg.exe). As soon as I
created the alias with that version, the application started working. I
removed the alias created with the 32 bit version.
Each version maintains a separate list of aliases. The registry key for the
32 bit vs. 64 bit is
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo &
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo,
respectively."
So, my suggestion is that you try to create the alias with both 32 and 64 bit version of
cliconfg.exe to see which it is that is required in your particular case (probably depends on
whether the client app is 32 or 64 bit - meguess).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Tim C" <TimC@.discussions.microsoft.com> wrote in message
news:098FFFB2-D352-4B16-A32D-CEA42461787C@.microsoft.com...
> There seems to be a subtle incompatibility issue. We have started moving our
> SQL 2000 servers to 32-bit OS's on virtual machines to avoid the issue.
> But if anyone knows of a simpler fix we could implement, I would love to
> hear it.
> Thanks,
> Tim C
> "Tim C" wrote:
>> SQL 2005 SP2 on Windows Server 2003 SP2
>> SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
>> Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
>> 32-bit. All use 32-bit SQL 2000.
>> Trying to create an Alias on a SQL 2000 machine to point to a named instance
>> on a SQL 2005 machine through TCP/IP (for use in replication).
>> When the alias is created on those SQL 2000 servers running a 32-bit OS, it
>> works.
>> When the alias is created on those SQL 2000 servers running a 64-bit OS, it
>> doesn't.
>> Instead, when I try to test using isql, I get:
>> DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
>> Una
>> ble to connect: SQL Server does not exist or network access denied.
>> Net-Library error 53: ConnectionOpen (Connect()).
>> Any ideas?
>> Thanks,
>> Tim C
SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
32-bit. All use 32-bit SQL 2000.
Trying to create an Alias on a SQL 2000 machine to point to a named instance
on a SQL 2005 machine through TCP/IP (for use in replication).
When the alias is created on those SQL 2000 servers running a 32-bit OS, it
works.
When the alias is created on those SQL 2000 servers running a 64-bit OS, it
doesn't.
Instead, when I try to test using isql, I get:
DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
Una
ble to connect: SQL Server does not exist or network access denied.
Net-Library error 53: ConnectionOpen (Connect()).
Any ideas?
Thanks,
Tim CThere seems to be a subtle incompatibility issue. We have started moving our
SQL 2000 servers to 32-bit OS's on virtual machines to avoid the issue.
But if anyone knows of a simpler fix we could implement, I would love to
hear it.
Thanks,
Tim C
"Tim C" wrote:
> SQL 2005 SP2 on Windows Server 2003 SP2
> SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
> Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
> 32-bit. All use 32-bit SQL 2000.
> Trying to create an Alias on a SQL 2000 machine to point to a named instance
> on a SQL 2005 machine through TCP/IP (for use in replication).
> When the alias is created on those SQL 2000 servers running a 32-bit OS, it
> works.
> When the alias is created on those SQL 2000 servers running a 64-bit OS, it
> doesn't.
> Instead, when I try to test using isql, I get:
> DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
> Una
> ble to connect: SQL Server does not exist or network access denied.
> Net-Library error 53: ConnectionOpen (Connect()).
> Any ideas?
> Thanks,
> Tim C|||I recently had a discussion in .tools about this. Paul O'kasick was nice enough to share his
findings. Aparently there's both a 32 and a 64 bit version of cliconfg.exe and these modify
different registry keys. Here's a quote from Paul most recent reply:
"The alias is working on our test machine. It turns out there is a 64 bit
version of cliconfg.exe (C:\WINDOWS\SysWOW64\cliconfg.exe). As soon as I
created the alias with that version, the application started working. I
removed the alias created with the 32 bit version.
Each version maintains a separate list of aliases. The registry key for the
32 bit vs. 64 bit is
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo &
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo,
respectively."
So, my suggestion is that you try to create the alias with both 32 and 64 bit version of
cliconfg.exe to see which it is that is required in your particular case (probably depends on
whether the client app is 32 or 64 bit - meguess).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Tim C" <TimC@.discussions.microsoft.com> wrote in message
news:098FFFB2-D352-4B16-A32D-CEA42461787C@.microsoft.com...
> There seems to be a subtle incompatibility issue. We have started moving our
> SQL 2000 servers to 32-bit OS's on virtual machines to avoid the issue.
> But if anyone knows of a simpler fix we could implement, I would love to
> hear it.
> Thanks,
> Tim C
> "Tim C" wrote:
>> SQL 2005 SP2 on Windows Server 2003 SP2
>> SQL 2000 SP4 on Windows Server 2003 SP2, with SQL 2005 Native Client installed
>> Some of the servers running SQL 2000 are using a 64-bit OS, some are usiing
>> 32-bit. All use 32-bit SQL 2000.
>> Trying to create an Alias on a SQL 2000 machine to point to a named instance
>> on a SQL 2005 machine through TCP/IP (for use in replication).
>> When the alias is created on those SQL 2000 servers running a 32-bit OS, it
>> works.
>> When the alias is created on those SQL 2000 servers running a 64-bit OS, it
>> doesn't.
>> Instead, when I try to test using isql, I get:
>> DB-Library: Unable to connect: SQL Server is unavailable or does not exist.
>> Una
>> ble to connect: SQL Server does not exist or network access denied.
>> Net-Library error 53: ConnectionOpen (Connect()).
>> Any ideas?
>> Thanks,
>> Tim C
Friday, February 24, 2012
Again: eMail subscription
I got a clue what might be wrong on my server machines which do not allow
eMail subscription due to a "configuration error"
I have an XP machine here with a local SQL server and a local RS client and
server. If I look at the property page of a given report there is always
something like that (I have to translate it from german, so maybe it is a
bit different in english versions):
changed at: (datetime)
changed by: SPONGEBOB\roland
created at: (datetime)
created by: SPONGEBOB\roland
size: 8kb
SPONGEBOB is the name of the machine; roland the user account.
Whereas my server machines show up the following:
changed at: (datetime)
changed by: TACCO\Administrator (unknown)
created at: (datetime)
created by: TACCO\Administrator (unknown)
size: 8kb
TACCO is the server name; administrator the user account. My concern is the
"unknown", what exactly causes the problem with eMail subscription. What
does cause RS to print "unknown" there and how to come over it?
TIA
rolandHallo Roland,
ich hatte ein ähnliches Problem, nachdem ich das Konto unter dem der Dienst läuft geändert hatte, ich mu�te es in den Orginalzustand zurücksetzen dann gingen auch wieder die eMail Abbonements.
Hi Roland,
I had a similar problem, but after resetting the account of the servce back to the one I've used while installing, the email works!
hth
sequal
"Roland" wrote:
> I got a clue what might be wrong on my server machines which do not allow
> eMail subscription due to a "configuration error"
> I have an XP machine here with a local SQL server and a local RS client and
> server. If I look at the property page of a given report there is always
> something like that (I have to translate it from german, so maybe it is a
> bit different in english versions):
> changed at: (datetime)
> changed by: SPONGEBOB\roland
> created at: (datetime)
> created by: SPONGEBOB\roland
> size: 8kb
> SPONGEBOB is the name of the machine; roland the user account.
> Whereas my server machines show up the following:
> changed at: (datetime)
> changed by: TACCO\Administrator (unknown)
> created at: (datetime)
> created by: TACCO\Administrator (unknown)
> size: 8kb
> TACCO is the server name; administrator the user account. My concern is the
> "unknown", what exactly causes the problem with eMail subscription. What
> does cause RS to print "unknown" there and how to come over it?
> TIA
> roland
>
>|||Me again, let it run under: "NT AUTHORITY\NetworkService"
sequal
"Roland" wrote:
> I got a clue what might be wrong on my server machines which do not allow
> eMail subscription due to a "configuration error"
> I have an XP machine here with a local SQL server and a local RS client and
> server. If I look at the property page of a given report there is always
> something like that (I have to translate it from german, so maybe it is a
> bit different in english versions):
> changed at: (datetime)
> changed by: SPONGEBOB\roland
> created at: (datetime)
> created by: SPONGEBOB\roland
> size: 8kb
> SPONGEBOB is the name of the machine; roland the user account.
> Whereas my server machines show up the following:
> changed at: (datetime)
> changed by: TACCO\Administrator (unknown)
> created at: (datetime)
> created by: TACCO\Administrator (unknown)
> size: 8kb
> TACCO is the server name; administrator the user account. My concern is the
> "unknown", what exactly causes the problem with eMail subscription. What
> does cause RS to print "unknown" there and how to come over it?
> TIA
> roland
>
>|||Hallo sequal,
wir haben es sowohl unter System als auch unter NetworkServices installiert.
Leider hat bei uns zumindest nichts geholfen. Unsere Server gehören zu
keiner Domain, ist das bei Euch anders?
we tried to install RS under "NTAUTHORITY\System" as well as NetworkService.
Nothing did help. Our servers don't belong to a domain, is that different at
your side?
r.|||Hallo Roland,
checken Sie doch bitte mal Ihre LogFiles, \Programme\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles. Ich hatte exact die selbe Fehlemeldung nachdem ich den User unter dem die RS laufen sollten geändert habe, die Daten in der RepServ DB werden verschlüsselt, und im Logfile finden Sie zur geplanten Laufzeit der e-Mailsubscribtion eine entsprechende Fehlermeldung.
Unsere System läuft in einem ActivDirectory (Domäne) ich hatte alles in einer Testumgebung aufgesetzt (keine Domäne) und dann ins Echtnetzwerk übertragen, als ich die User unter welchen solche Dienste bei uns in der Firma laufen nachgepflegt habe ging plötzlich die e-Mail Subs. nicht mehr, aber alles andere lief.
Grüsse s.
P.S.: Anbei ein Auszug aus meinem Logfile welches mir den HinweiÃ? gab:
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Initializing crypto as user: NT-AUTORITÃ?T\SYSTEM
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Exporting public key
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Performing sku validation
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Importing existing encryption key
ReportingServicesService!library!d18!25.05.2004-16:08:20:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: Der Berichtsserver kann den symmetrischen Schlüssel nicht entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden Sie in der Dokumentation., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: Der Berichtsserver kann den symmetrischen Schlüssel nicht entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden Sie in der Dokumentation. --> System.Runtime.InteropServices.COMException (0x80090005): Ungültige Daten
"Roland" wrote:
> Hallo sequal,
> wir haben es sowohl unter System als auch unter NetworkServices installiert.
> Leider hat bei uns zumindest nichts geholfen. Unsere Server gehören zu
> keiner Domain, ist das bei Euch anders?
> we tried to install RS under "NTAUTHORITY\System" as well as NetworkService.
> Nothing did help. Our servers don't belong to a domain, is that different at
> your side?
> r.
>
>|||Sequal,
Danke für Deine/Ihre Bemühungen.
In
news:ucIk$9uVEHA.1152@.TK2MSFTNGP09.phx.gbl
habe ich mal die Inhalte der Logdateien dargestellt. Irgendwie matchen die
nicht Deine/Ihre Logs :)
Grüsse und Vielen Dank
Roland
"sequal" <sequal@.discussions.microsoft.com> schrieb im Newsbeitrag
news:67196D21-20B2-4B62-A09A-32E9F7DEFEA7@.microsoft.com...
> Hallo Roland,
> checken Sie doch bitte mal Ihre LogFiles, \Programme\Microsoft SQL
Server\MSSQL\Reporting Services\LogFiles. Ich hatte exact die selbe
Fehlemeldung nachdem ich den User unter dem die RS laufen sollten geändert
habe, die Daten in der RepServ DB werden verschlüsselt, und im Logfile
finden Sie zur geplanten Laufzeit der e-Mailsubscribtion eine entsprechende
Fehlermeldung.
> Unsere System läuft in einem ActivDirectory (Domäne) ich hatte alles in
einer Testumgebung aufgesetzt (keine Domäne) und dann ins Echtnetzwerk
übertragen, als ich die User unter welchen solche Dienste bei uns in der
Firma laufen nachgepflegt habe ging plötzlich die e-Mail Subs. nicht mehr,
aber alles andere lief.
> Grüsse s.
> P.S.: Anbei ein Auszug aus meinem Logfile welches mir den Hinweiß gab:
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Initializing crypto as user: NT-AUTORITÄT\SYSTEM
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Exporting public key
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Performing sku validation
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Importing existing encryption key
> ReportingServicesService!library!d18!25.05.2004-16:08:20:: e ERROR:
Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledExcept
ion: Der Berichtsserver kann den symmetrischen Schlüssel nicht
entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in
einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen
Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten
Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden
Sie in der Dokumentation., ;
> Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledExcept
ion: Der Berichtsserver kann den symmetrischen Schlüssel nicht
entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in
einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen
Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten
Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden
Sie in der Dokumentation. --> System.Runtime.InteropServices.COMException
(0x80090005): Ungültige Daten
>
> "Roland" wrote:
> > Hallo sequal,
> >
> > wir haben es sowohl unter System als auch unter NetworkServices
installiert.
> > Leider hat bei uns zumindest nichts geholfen. Unsere Server gehören zu
> > keiner Domain, ist das bei Euch anders?
> >
> > we tried to install RS under "NTAUTHORITY\System" as well as
NetworkService.
> > Nothing did help. Our servers don't belong to a domain, is that
different at
> > your side?
> >
> > r.
> >
> >
> >
eMail subscription due to a "configuration error"
I have an XP machine here with a local SQL server and a local RS client and
server. If I look at the property page of a given report there is always
something like that (I have to translate it from german, so maybe it is a
bit different in english versions):
changed at: (datetime)
changed by: SPONGEBOB\roland
created at: (datetime)
created by: SPONGEBOB\roland
size: 8kb
SPONGEBOB is the name of the machine; roland the user account.
Whereas my server machines show up the following:
changed at: (datetime)
changed by: TACCO\Administrator (unknown)
created at: (datetime)
created by: TACCO\Administrator (unknown)
size: 8kb
TACCO is the server name; administrator the user account. My concern is the
"unknown", what exactly causes the problem with eMail subscription. What
does cause RS to print "unknown" there and how to come over it?
TIA
rolandHallo Roland,
ich hatte ein ähnliches Problem, nachdem ich das Konto unter dem der Dienst läuft geändert hatte, ich mu�te es in den Orginalzustand zurücksetzen dann gingen auch wieder die eMail Abbonements.
Hi Roland,
I had a similar problem, but after resetting the account of the servce back to the one I've used while installing, the email works!
hth
sequal
"Roland" wrote:
> I got a clue what might be wrong on my server machines which do not allow
> eMail subscription due to a "configuration error"
> I have an XP machine here with a local SQL server and a local RS client and
> server. If I look at the property page of a given report there is always
> something like that (I have to translate it from german, so maybe it is a
> bit different in english versions):
> changed at: (datetime)
> changed by: SPONGEBOB\roland
> created at: (datetime)
> created by: SPONGEBOB\roland
> size: 8kb
> SPONGEBOB is the name of the machine; roland the user account.
> Whereas my server machines show up the following:
> changed at: (datetime)
> changed by: TACCO\Administrator (unknown)
> created at: (datetime)
> created by: TACCO\Administrator (unknown)
> size: 8kb
> TACCO is the server name; administrator the user account. My concern is the
> "unknown", what exactly causes the problem with eMail subscription. What
> does cause RS to print "unknown" there and how to come over it?
> TIA
> roland
>
>|||Me again, let it run under: "NT AUTHORITY\NetworkService"
sequal
"Roland" wrote:
> I got a clue what might be wrong on my server machines which do not allow
> eMail subscription due to a "configuration error"
> I have an XP machine here with a local SQL server and a local RS client and
> server. If I look at the property page of a given report there is always
> something like that (I have to translate it from german, so maybe it is a
> bit different in english versions):
> changed at: (datetime)
> changed by: SPONGEBOB\roland
> created at: (datetime)
> created by: SPONGEBOB\roland
> size: 8kb
> SPONGEBOB is the name of the machine; roland the user account.
> Whereas my server machines show up the following:
> changed at: (datetime)
> changed by: TACCO\Administrator (unknown)
> created at: (datetime)
> created by: TACCO\Administrator (unknown)
> size: 8kb
> TACCO is the server name; administrator the user account. My concern is the
> "unknown", what exactly causes the problem with eMail subscription. What
> does cause RS to print "unknown" there and how to come over it?
> TIA
> roland
>
>|||Hallo sequal,
wir haben es sowohl unter System als auch unter NetworkServices installiert.
Leider hat bei uns zumindest nichts geholfen. Unsere Server gehören zu
keiner Domain, ist das bei Euch anders?
we tried to install RS under "NTAUTHORITY\System" as well as NetworkService.
Nothing did help. Our servers don't belong to a domain, is that different at
your side?
r.|||Hallo Roland,
checken Sie doch bitte mal Ihre LogFiles, \Programme\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles. Ich hatte exact die selbe Fehlemeldung nachdem ich den User unter dem die RS laufen sollten geändert habe, die Daten in der RepServ DB werden verschlüsselt, und im Logfile finden Sie zur geplanten Laufzeit der e-Mailsubscribtion eine entsprechende Fehlermeldung.
Unsere System läuft in einem ActivDirectory (Domäne) ich hatte alles in einer Testumgebung aufgesetzt (keine Domäne) und dann ins Echtnetzwerk übertragen, als ich die User unter welchen solche Dienste bei uns in der Firma laufen nachgepflegt habe ging plötzlich die e-Mail Subs. nicht mehr, aber alles andere lief.
Grüsse s.
P.S.: Anbei ein Auszug aus meinem Logfile welches mir den HinweiÃ? gab:
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Initializing crypto as user: NT-AUTORITÃ?T\SYSTEM
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Exporting public key
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Performing sku validation
ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO: Importing existing encryption key
ReportingServicesService!library!d18!25.05.2004-16:08:20:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: Der Berichtsserver kann den symmetrischen Schlüssel nicht entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden Sie in der Dokumentation., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: Der Berichtsserver kann den symmetrischen Schlüssel nicht entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden Sie in der Dokumentation. --> System.Runtime.InteropServices.COMException (0x80090005): Ungültige Daten
"Roland" wrote:
> Hallo sequal,
> wir haben es sowohl unter System als auch unter NetworkServices installiert.
> Leider hat bei uns zumindest nichts geholfen. Unsere Server gehören zu
> keiner Domain, ist das bei Euch anders?
> we tried to install RS under "NTAUTHORITY\System" as well as NetworkService.
> Nothing did help. Our servers don't belong to a domain, is that different at
> your side?
> r.
>
>|||Sequal,
Danke für Deine/Ihre Bemühungen.
In
news:ucIk$9uVEHA.1152@.TK2MSFTNGP09.phx.gbl
habe ich mal die Inhalte der Logdateien dargestellt. Irgendwie matchen die
nicht Deine/Ihre Logs :)
Grüsse und Vielen Dank
Roland
"sequal" <sequal@.discussions.microsoft.com> schrieb im Newsbeitrag
news:67196D21-20B2-4B62-A09A-32E9F7DEFEA7@.microsoft.com...
> Hallo Roland,
> checken Sie doch bitte mal Ihre LogFiles, \Programme\Microsoft SQL
Server\MSSQL\Reporting Services\LogFiles. Ich hatte exact die selbe
Fehlemeldung nachdem ich den User unter dem die RS laufen sollten geändert
habe, die Daten in der RepServ DB werden verschlüsselt, und im Logfile
finden Sie zur geplanten Laufzeit der e-Mailsubscribtion eine entsprechende
Fehlermeldung.
> Unsere System läuft in einem ActivDirectory (Domäne) ich hatte alles in
einer Testumgebung aufgesetzt (keine Domäne) und dann ins Echtnetzwerk
übertragen, als ich die User unter welchen solche Dienste bei uns in der
Firma laufen nachgepflegt habe ging plötzlich die e-Mail Subs. nicht mehr,
aber alles andere lief.
> Grüsse s.
> P.S.: Anbei ein Auszug aus meinem Logfile welches mir den Hinweiß gab:
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Initializing crypto as user: NT-AUTORITÄT\SYSTEM
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Exporting public key
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Performing sku validation
> ReportingServicesService!crypto!d18!25.05.2004-16:08:20:: i INFO:
Importing existing encryption key
> ReportingServicesService!library!d18!25.05.2004-16:08:20:: e ERROR:
Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledExcept
ion: Der Berichtsserver kann den symmetrischen Schlüssel nicht
entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in
einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen
Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten
Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden
Sie in der Dokumentation., ;
> Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledExcept
ion: Der Berichtsserver kann den symmetrischen Schlüssel nicht
entschlüsseln, der zum Zugreifen auf geschützte oder verschlüsselte Daten in
einer Berichtsserver-Datenbank verwendet wird. Sie müssen entweder einen
Sicherungsschlüssel wiederherstellen oder den gesamten verschlüsselten
Inhalt löschen und den Dienst dann neu starten. Weitere Informationen finden
Sie in der Dokumentation. --> System.Runtime.InteropServices.COMException
(0x80090005): Ungültige Daten
>
> "Roland" wrote:
> > Hallo sequal,
> >
> > wir haben es sowohl unter System als auch unter NetworkServices
installiert.
> > Leider hat bei uns zumindest nichts geholfen. Unsere Server gehören zu
> > keiner Domain, ist das bei Euch anders?
> >
> > we tried to install RS under "NTAUTHORITY\System" as well as
NetworkService.
> > Nothing did help. Our servers don't belong to a domain, is that
different at
> > your side?
> >
> > r.
> >
> >
> >
Subscribe to:
Posts (Atom)