Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Network logon prompt when running crystal report

Status
Not open for further replies.

theoryofben

IS-IT--Management
Aug 25, 2001
149
US
Hello All. I have a strange problem that I have never had before. Any help is greatly appreciated.

My app is an intranet app that utilizes a crystal report. The report is located in the same directory as the other site files.

It was working great, but now when we get to the page with the report, it brings up a username/password prompt (the type you get when trying to browse another pc on the domain).

If I put in my info (I'm a domain admin), it works fine. But if I cancel, it bring up the error page saying that access is denied to "C:\\Documents and settings\pcname\ASPNET\Local Settings\Temp\longtempfilename.rpt
I gave full permissions for that folder but it still happens.

Does anyone have any idea what's going on? Is this a configuration problem? This isn't the first app we've deployed on this server using crystal reports.

________________________________________________
"I have not failed. I've just found 10,000 ways that won't work."-Thomas Edison

 
do the users group have rights as well.. users and aspnet should have rights to that folder on your IIS server.

 
Yes, I gave everyone full control just to try and narrow down the problem.

The thing is, my report is located in the project folder under inetpub/ But the problem directory seems to be a temp directory that ASPNET uses on it's own. Is there a way to configure .net to not do that?

The strange thing is, I have another app on the same server that uses a crystal report in the same way and it is still functioning fine.


________________________________________________
"I have not failed. I've just found 10,000 ways that won't work."-Thomas Edison

 
Yes (I think). The report was working fine before the other day. And it will load fine now (if you put in your credentials).

The only thing that changed was that we changed the password of a domain account that was used to link to the server when I set the project up. I'm guessing now that it cached the credential info and that is why it worked fine until we changed the password of the domain account. So, that's why it is now asking for new credentials.

So, maybe the this problem has been here all along. I may just create a deployment package and intall it. Do you think that may solve the problem? I would really like to know what's causing it though.


________________________________________________
"I have not failed. I've just found 10,000 ways that won't work."-Thomas Edison

 
if your pushing the report and using a dataset, in your connection string you will need to put in the new password and rebuild the project and replace those pages in IIS for the prompt to go away.

 
Ok, it's working (for now). I have no idea why it is working. I changed the build action for the rpt to 'None' and built the project. The report would not load like that, so I changed it back to 'Embedded Resource' and now it is not asking for the information.

It was asking for a network logon for the web server not for the sql connection. I'm using the pull method and sending an input parameter. I've specified my sql connection info in code and that has always worked fine.

Even though it is working now, I'm still very uncomfortable with it. I have no idea why the error was happening or how it got fixed. We are starting a beta test on the 15th and this makes me very skittish.

I appreciate your help on this.

________________________________________________
"I have not failed. I've just found 10,000 ways that won't work."-Thomas Edison

 
well, if that's the case, you have a IIS problem. if you are using a dataset for your CR and on your page load event using a connection string to connect, you should not get prompted for a user name and password. and make sure aspnet and users have access to you app directory.


under build action it should embeded
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top