Interesting Password Glitch

  • I have created some users with a password with an "!" at the end and although, everything seems fine and tests fine. When we run a report against the database with that user, it refuses to work. Remove the "!" from the password and it works again. We have not tested whether the "!" is a problem or the fact that it is at the end of the password. Does anyone know why this is? I thought "!"s were perfectly legal in a password.

  • hi,

    how are you running the reports ?

    Paul

  • Hi Paul

    We use MSSQL reporting Services. An odbc link is setup, which works fine one can see the DB through the DSN and the tests work fine. Once one uses the wizard to setup a new report where you specify the Datasource it must use, it tells you it cannot connect if the password has the "!" in it.

    José

  • Did not we have a question QOD yesterday what is the comment sign in XML? The answer was <!--   -->  maybe the web page does not like the ! mark?

    Regards,Yelena Varsha

  • Hi Yelena

    thanks for the response.

    I guess that is possible, but I can only imagine that if it were converted to XML it may look something like this

    <password><"12345!"></password> 

    (I'm not an XML expert and it probably shows), but just for illustration purposes I think this will do and I can assure you that there are no "--" in the password. So I'm not convinced that is the answer, but then again, at this stage your guess is a good as mine.

    Thanks again

    José

  • Jose,

    It was just an example.

    I tested creating a report with Wizard and used a user who has a password that ends with ! It worked, but I had to deploy only the rdl file:

    I have SQL Server 2005 on my laptop that installs some of Visual Studio 2005. I used it to select Report Wizard project and created a simple report. When I tried to deploy it to my SQL Server 2000 reporting Services it did not work because of difference in the version. So I used only RDL file, moved in manually and imported into Report Server. I had to change the header from 2005 to 2003 in the file as follows. I had to change 2005/01 to 2003/10 in the following line:

    <Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">

    This report works for the user who has a password that ends with ! Here is a Data Source part of report definition. Let me know if your definition is similar and what version of Visual Studio you are using and what is a version of your report server. Maybe the trick is in the Data Source definition.

    <DataSources>

    <DataSource Name="Test2">

    <rdataSourceID>e603d038-fbd2-4037-8313-8324af0ad172</rdataSourceID>

    <ConnectionProperties>

    <DataProvider>SQL</DataProvider>

    <ConnectString>Data Source=MyServerName;Initial Catalog=MyDatabaseName</ConnectString>

    <Prompt>Specify a user name and password for data source clartest1</Prompt>

    </ConnectionProperties>

    </DataSource>

    </DataSources>

    P.S. I don't know why the : D (:sign and letter D) was replaced by smiling faces in Data Source ID when I publish my reply, it looks fine in the Edit mode of this post. I had put a space between them in this P.S.

    Regards,Yelena Varsha

  • Yelena

    Thanks, you put us on the right track. We had a horrible mixture of versions. We were trying to run SQL 2000 Reporting services, against MSSQL2005, using Visual Studio 2003. Once we got everything to the 2005, the problem disappeared.

    Thanks again for your patience and time.

     

    Regards

    José

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply