Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
nicklarge
Starting Member
40 Posts |
 Posted - 2011-10-11 : 16:09:08
|
| Hello.I am having an interesting situation with deploying reports in SSRS 2008 and wonder if anyone else has had the same.I have a report that pushes successfully to both integration and production environments. The result of SELECT @@VERSION on each is as such:Production: (RTM)Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2) Integration: (SP1)Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2) Then I get a request that meant that I had to trim leading zeros off of the customer number in the main query. The easiest way for me to do that was to simply convert to an int and back to a varchar, kinda similar to the following:(From) SELECT customernumber as [Customer Number] FROM mydb(to) SELECT convert(varchar(20), convert(int, customernumber)) as [customer Number] from mydbof course my query is actually bigger, but I dont want to complicate the issue here so I've provided the example above.My issue is that when I pushed the report with the changes to integration it did as expected, but when I pushed to production it prompted me for authentication, and kept doing so even though my credentials were correct. Kinda like refusal to push to production !? I took the section back out again (undid my changes) and pushed to production successfully without the additional prompting.Has anyone had this experience before? It appears that when a "convert(int, {resource})" is implemented, that the application is incapable of pushing to production successfully. Really weird.Thanks in advance, Nick. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-10-12 : 01:32:02
|
| which is application you're using to deploy? also do you have access to deploy reports to production? When you're removing the convert are you able to deploy to same location?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
nicklarge
Starting Member
40 Posts |
Posted - 2011-10-12 : 13:41:41
|
| Visakh16,When I remove the convert(int, ...) it does deploy to production. We managed to find a resolve for the issue, but not identify the root cause of the issue. I found this link : http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=59835 which helped us to get the report to the production environment. Basically, when I tried to push the report with the convert(int, ...) from my local machine using the report manager it did not work. Based on the information given in the topic, I asked a DBA to remote to the production server, copy the rdl to the local disk on the server, and push using report manager, locally. It worked. This is really odd and I have no idea where to start to try and identify the actual "fix" for the issue, but for now we have a work around. I wonder if it is something to do with authentication on the production server? I dont understand why that would be the case though because the only change is converting to int ... ?? How would that affect whether it authenticates during deployment ?? I'm very confused. |
|
|
|
|
|
|
|
|
Strange deployment issue SSRS 2008 R2