Skip to main content

Posts

Showing posts from March, 2010

Sys.ArgumentException: Cannot deserialize. The data does not correspond to valid JSON.

I face the problem today and sick to resolve it thanks for Henrik Juhlin who post the solution here and i will do following more changes get rid of this issue http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/329762/scope/posts/Default.aspx Update following files from dnn 5.0.1 dnn installation setup to Main JS folder js/dnn.xml.js js/dnn.xml.jsparser.js js/dnn.xmlhttp.js js/dnn.xmlhttp.jsxmlhttprequest.js Note very important : after that clear your cache and close the browser. Execute the application again in new browser Regards Rashid Imran Bilgrami CEO Best Visualization

Unable to open configSource file 'connectionstrings.config'.

Today i got the error during the removal of virus activity at my server i got the error Parser Error Message: Unable to open configSource file 'connectionstrings.config'. Solution just copy the connectionstrings.config in to your desiger location from root the problem will be resolved Regards CEO Bestvisualization Rashid Imran Bilgrami

DNN Blog: Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces

Dear all, Today i was faced a problem problem setting up Blog module, one of the exception blocks is shown below: Error: Blog is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnect