One of my colleague wrote a stored procedure in which he was just truncating a table. On calling that SP from a BO developed in .Net 4.0 we got a message as below
"Cannot find object \"xxx\" or you dont have permissions"
The fun part was when we started the SQL Profiler it showed us that it has ran the SP without any errors. There was no error in EVENTVWR too.
On trying multiple options, I ended up giving OWNER rights to NETWORKSERVICE (the login which our service was hosted with) and it worked properly.
Showing posts with label sql 2005. Show all posts
Showing posts with label sql 2005. Show all posts
Friday, December 31, 2010
Tuesday, January 5, 2010
The setup failed to read IIsMimeMap table. The error code is -2147023550.
I've been facing issues with installation of Reporting service 2005 and making it run but for the first time I faced an issue while uninstalling it. On trying to uninstall I got the following error
"The setup failed to read IIsMimeMap table. The error code is -2147023550"
Solution:
1. Stop IIS Admin service
2. Stop IIS
3. Uninstall Reporting service.
Result:
Successfully uninstalled Reporting service 2005
"The setup failed to read IIsMimeMap table. The error code is -2147023550"
Solution:
1. Stop IIS Admin service
2. Stop IIS
3. Uninstall Reporting service.
Result:
Successfully uninstalled Reporting service 2005
ASP .Net Service account appears blank
Its been time I got a chance to trouble shoot a Reporting Service Problem, and this time it was on Windows 7. Actually I faced this issue once before and I managed to skip trouble shooting that.
Reading the initial "Program incompatible message" on running the setup of SQL 2005 I came to know that its necessary to install SP3 for SQL 2005 to run on Windows 7. I downloaded it and installed successfully.
On opening (my favorite) Reporting service Configuration tool, I observed that the "ASP .Net Service Account" appeared blank and because of that I was not able to change the Application pool to ReportServer (which is created by default)
Reading few blogs I changed the Application Pool to Reportserver (from DefaultAppPool) using IIS-> Advanced Settings
But still the problem of the ASP .Net service account was lingering.
I ran the following command to get the service account appear in the configuration tool.
aspnet_regiis -ga "NT Authority\NetworkService"
Reading the initial "Program incompatible message" on running the setup of SQL 2005 I came to know that its necessary to install SP3 for SQL 2005 to run on Windows 7. I downloaded it and installed successfully.
On opening (my favorite) Reporting service Configuration tool, I observed that the "ASP .Net Service Account" appeared blank and because of that I was not able to change the Application pool to ReportServer (which is created by default)
Reading few blogs I changed the Application Pool to Reportserver (from DefaultAppPool) using IIS-> Advanced Settings
But still the problem of the ASP .Net service account was lingering.
I ran the following command to get the service account appear in the configuration tool.
aspnet_regiis -ga "NT Authority\NetworkService"
Wednesday, August 12, 2009
Change in PC name, stops Reporting Service 2005
I deployed few reports on my Test Machine with TestMachine. As we wanted to implement a format of PC names, we happened to change the name of the Machine to e.g CompanyTestMachine
Before the rename happened, our system as well as the reports were working properly. Once the name was changed, we started getting error Report Server database not found.
Then I thought to redo the settings of Reporting service so as to change the required settings. On following the steps, I came across a error
User CompanyTestMachine\ASPNet not found
I then tried repairing the Microsoft Framework which didnt help. I ran the aspnet_regiis.exe /i command which also didn't help. I read many blogs but couldn't find a way out so I ended up renaming the machine to its original name.
I am still searching for a solution to this problem, if someone reading this has one I would appreciate if you could share it with me.
Before the rename happened, our system as well as the reports were working properly. Once the name was changed, we started getting error Report Server database not found.
Then I thought to redo the settings of Reporting service so as to change the required settings. On following the steps, I came across a error
User CompanyTestMachine\ASPNet not found
I then tried repairing the Microsoft Framework which didnt help. I ran the aspnet_regiis.exe /i command which also didn't help. I read many blogs but couldn't find a way out so I ended up renaming the machine to its original name.
I am still searching for a solution to this problem, if someone reading this has one I would appreciate if you could share it with me.
Wednesday, May 20, 2009
Error (rsAccessDenied) - 'NT AUTHORITY\NETWORK SERVICE' are insufficient
I did all the necessary settings to the reporting service so that my domain users can access the reporting service, but still I was getting rsAccessDenied error.
Then I read once solution in one of the forums in which there were few steps mentioned which solved my problem
1. Open http://localhost/reports
2. Go to Home Properties
3. Add a BUILTIN\Users and gave it Browser permissions and the problem was solved.
Then I read once solution in one of the forums in which there were few steps mentioned which solved my problem
1. Open http://localhost/reports
2. Go to Home Properties
3. Add a BUILTIN\Users and gave it Browser permissions and the problem was solved.
TF30042: The database is full. Contact your Team Foundation Server administrator.
Since many days we were facing problems with Low disk space on our TFS machine. I noticed that the LoadTest database Log was around 19Gigs. Till then I was not aware that there is a setting for restricting growth of the Log file. I then moved my mdf and ldf files to a drive with ample space and then restricted the growth of Log not more than 20Gigs.
.jpg)
And subsequently I changed the settings of all the TFS database not to grow exponentially. But the next day I came and tried to start my VSTS, it started givine me the same error
TF30042: The database is full. Contact your Team Foundation Server administrator.
Reading few blogs, I decided to change the Recovery Model of all the database from full to simple. And I was able to use my TFS without any issues after that. Below are the steps
1. Go to properties of the database
2. In Options tab, change Recovery model from Full to Simple.
.jpg)
I read in couple of blogs that it is not advisable to use Full Recovery model for the database which is used for version control.
Subscribe to:
Posts (Atom)
.jpg)