"The procedure entry point _vswprintf_c_l could not be located in the dynamic link
library MSVCR80.dll."
What can be wrong?I would suggest posting this to SQL Server Setup & Upgrade forum for faster response.
Thanks,
-Vineet Rao
"The procedure entry point _vswprintf_c_l could not be located in the dynamic link
library MSVCR80.dll."
What can be wrong?I would suggest posting this to SQL Server Setup & Upgrade forum for faster response.
Thanks,
-Vineet Rao
When I try to run my application using VWD from the file system I can connect and run the application and it connects to the remote SQL 2000 server with no problem.
However, when I publish to my web server I get the folloiwng error message:
Anyone got any ideas??
Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message:The entry 'MCLConnectionString' has already been added.
Source Error:
Line 11: <appSettings/>Line 12: <connectionStrings>Line 13: <add name="MCLConnectionString" connectionString="Data Source=GEACO1INTR1;Initial Catalog=MCL;Persist Security Info=True;User ID=ASPNET;Password=PAUL0001" providerName="System.Data.SqlClient"/>Line 14: </connectionStrings>Line 15: <system.web>
I also notice that it works if I put the connection string in each form, but as soon as I try to add it to the web.config file I get the above error.
Thanks
Paul
|||My guess is that you have a ConnectionString with the same name on a Parent Web Application, my advise would be either to change the name of the ConnectionString, or do this:
<connectionString>
<clear/>
<add name="MCLConnectionString" connectionString="..." />
</connectionStrings
Hope this Helps,
Roberto Hernandez-Pou
http://www.rhpconsulting.net
IMPORTANT: If you use the <clear/> to clean all connectionString keys, you would also be removing the ones for the SqlAuthenticationProvider and SqlRoleProvider.
|||To add onto Roberto's reply...
If the MCLConnectionString does already exist higher in the configuration hierarchy, you don't have to add it again to use at this level. Remove it at this level's web.config and read the connection string as normal, and the configuration API will pick it up.
Don
|||Thanks, that sorted it. I had a copy of the web.config file left in the root directory of the web server.
Thanks again for your help
Paul
Error accessing report,sql error