In Reporting Services 2005 for some reason, you sometimes get this error:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online HelpSQL Server does not exist or access denied.
Along with a reference to not having named pipes installed.
To fix it, just run the following command:
rsconfig -c -sMyServerName -dReportServer -awindows -uDomain\Account -pMyPassword
Monday, August 7, 2006
Monday, July 31, 2006
Repairing SQL Reporting Services 2000
Occasionally SQL Server Reporting Services 2000 seems to mess up and give you install errors, or permission errors. Listed below are 2 very good fixes which seem to fix the majority of issues:
1) run this command: RSActivate -c -r “C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config”
2) try this knowledgebase article: http://support.microsoft.com/kb/887787
enjoy...
1) run this command: RSActivate -c -r “C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config”
2) try this knowledgebase article: http://support.microsoft.com/kb/887787
enjoy...
Monday, July 24, 2006
Internet SQL Reporting Server 2000
This is far too complex and poorly documented for my liking!
Microsoft recomend that you add this tag to the Reportserver Virtual Dir rswebapplication.config file:
www.domainName.com/reportServer
HOWEVER This is much easier
Delete the info in the section of rswebapplication.config
/ReportServer
and ensure that the ReportServer virtual directory in IIS is pointing to:
"C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager"
how good is that!
Microsoft recomend that you add this tag to the Reportserver Virtual Dir rswebapplication.config file:
HOWEVER This is much easier
Delete the info in the
and ensure that the ReportServer virtual directory in IIS is pointing to:
"C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager"
how good is that!
Thursday, June 15, 2006
Hacking Windows Passwords
If you ever lose your password and cannot acces your XP box, then download this tool
http://home.eunet.no/pnordahl/ntpasswd/bootdisk.html
You can burn it to CD or floppy, just boot your machine to it and you can view and reset all the local machine passwords. It also works on servers too, which can be a bit dangerous as i'm sure you can imagine...
http://home.eunet.no/pnordahl/ntpasswd/bootdisk.html
You can burn it to CD or floppy, just boot your machine to it and you can view and reset all the local machine passwords. It also works on servers too, which can be a bit dangerous as i'm sure you can imagine...
Sunday, June 4, 2006
Sharepoint homepage error
After doing some modifications to one of our Sharepoint sites, the homepage stopped working! However at the same time, all other Sharepoint sites were still responding. This caused me a lot of headache and stres... especially after spending hours on a new Sharepoint site.
After spending a Saturday morning looking into the problem, I found this knowledgebase article, which cured the problem + an iisreset..
http://support.microsoft.com/?id=826786
After spending a Saturday morning looking into the problem, I found this knowledgebase article, which cured the problem + an iisreset..
http://support.microsoft.com/?id=826786
Thursday, April 13, 2006
CRM 3 Email Settings
This Registry key hold all the mail server info:
MY Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
The SMTPServer key is worht checking if you can't send email through CRM 3
...
MY Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
The SMTPServer key is worht checking if you can't send email through CRM 3
...
Sunday, April 9, 2006
USERENV Errors in SBS2003
OK his is a part one fix of userenv errors in SBS2003 clients. RSOP.msc shows that group policy settings are not getting applied.
The problem seems to be partly due to cached logon credintials on the clients. To fi this do the following:
1) run control userpasswords2
2) Click the Advanced tab and click the Manage Passwords button, and then
remove any entry related to the problem account and domain.
Other articles suggest also forcing keberos to use tcp instead of udp
let me know your thoughts...
The problem seems to be partly due to cached logon credintials on the clients. To fi this do the following:
1) run control userpasswords2
2) Click the Advanced tab and click the Manage Passwords button, and then
remove any entry related to the problem account and domain.
Other articles suggest also forcing keberos to use tcp instead of udp
let me know your thoughts...
Subscribe to:
Posts (Atom)