javascript error on page of MS SQL Reporting Services - Datasource.aspx?createnew

Hi All,

 Still trying to learn SQL Server reporting services and having some trouble.

 I'm trying to create a new datasource (using the /reports virtual directory, not via visual studio)

 I created one before with no problems,

  Now on that page I get an javascript page and the familiar ! error sybol at the bottom left of IE

  The error is line 388 char 3 error: Object expected Code:0 Url

  Line 388 is pointless, becuase when I view source I get a file with 294 lines. (maybe it's including the contents of the external javascripts?)

  - Anyhow,

    After I installed RS, I had to move it to a differnent website (didn't need it on default) - that worked almost fine, except I got a few errors that seemed to be related to the lack of an SSL certificate - So I created one with cert server and installed it on IIS - I think its' around then that it stopped working, but hard to say, I've done a lot over the past 3 days.

  If this has ever happened to you, please post a reply, even if you don't have the answer so I can guage how common this is.


LVL 12
Who is Participating?
Bit of narrowing down...
Do other reports on your site work ok?
Is the issue just on creation of a datasource via Report Manager?

Check this article for non-default IIS site setup:

Moving Reporting Services' Virtual Directories
fruhjAuthor Commented:
Hey Simon,

  It seems to be just the datasource.aspx page. Reports are showing fine and the other screens I've accessed via the /reports virtual directory all seem fine as well (they render to IE fine with no javascript errors)

I've got a test server here (without the error) I think I'll do an MD5 checksum on the folders and compare it to an MD5 of the problem server to verify that the files are the same - then at least we can rule out the aspx and js files as the problem.
fruhjAuthor Commented:
Hi Again Simon,

I did the MD5 and all files are the same, minus 2 config files that were mentioned in the article.

I noticed something else today that might help:

I can't add a new folder - the ok button doesnt do anything - leads me to think it's not getting the javascript file or something.
However that' the case testing from the new site I have setup (copied the folders per your article)

On the original "default web site", I am able to add a folder.
Both point to the same RS code - so it must be something different - maybe permissions setup, maybe config file, maybe the .net include files aren't in the new site I setup (I tried a test aspx page and it works, but it didn't use any client side javascript for validation - so maybe I'm missing that on my new site?)

Ok Simon, thanks again, if you think of anything else, please let me know!

- Jack
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

fruhjAuthor Commented:
Hey Simon, that was it!

How F**ing Stupid of me!

I thought I followed your article, and obviously I missed the last step - copying the asp_net client.

(I never got the error message about not finding the js file from IE or I'm sure I'd figured this one out sooner)

Anyhow Simon, once again thanks for all your help on this question and questions you've helped me out in the past with!

- Jack
fruhjAuthor Commented:
Follow up message for someone reading this in the PAQ

I had a problem with reporting services on a new site I had created.

Many of the problems were related to client side buttons not working.

It turned out to be a missing javascript file on the new site I created. uses a .js file for it's client side javascript code - used in things like validation, etc...

I had created a new site, and aspx files were working, so I forgot all about the js file.

I copied the folder: aspnet_client from another site off my machine (the default site to be exact) into the site I had used for Reporting services.

This fixed the problem.

Hopefully this paq can help someone else!
Glad I could be of help
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.