Thursday, September 30, 2010
Map a sharepoint document folder to a network drive
9:44 AM | Posted by
Unknown |
Edit Post
This article doesn't solve the mapping problem, but it lets you open a Sharepoint folder in Windows Explorer on Win XP...
Map sharepoint document folder to a network drive - Outlook by the sound: "'\\Servername:portnumber\sites\mysite\Shared%20Documents\'
The port is not supported by Windows folder sharing. The UNC name folder sharing path can only use the machine name appending the folder.
The port concept can't be applied here; it should be used with the HTTP url.
We can specify http url as the sharing path. The steps is listed for you below:
1. At the File explorer, please click the 'Tools->Map Network Drive'
2. at the window, please click the link 'Sign up for ...'
3. at the pop-up window, click next, next and input the url. For example: http://mysps:2005/Shared20Documents
4. click ok to set up this mapping.
Map sharepoint document folder to a network drive - Outlook by the sound: "'\\Servername:portnumber\sites\mysite\Shared%20Documents\'
The port is not supported by Windows folder sharing. The UNC name folder sharing path can only use the machine name appending the folder.
The port concept can't be applied here; it should be used with the HTTP url.
We can specify http url as the sharing path. The steps is listed for you below:
1. At the File explorer, please click the 'Tools->Map Network Drive'
2. at the window, please click the link 'Sign up for ...'
3. at the pop-up window, click next, next and input the url. For example: http://mysps:2005/Shared20Documents
4. click ok to set up this mapping.
Wednesday, September 22, 2010
CRM 4.0 Workflow, Imports and Outlook Client don't work!!!
5:08 PM | Posted by
Unknown |
Edit Post
Here is a lift from Robert MacLean's blog. Thank you Robert for posting this!
Workflow doesn't work, Imports never happen, emails don't flow and Outlook clients cannot connect
Wed, 01/23/2008 - 14:18 | Robert MacLean
Update 23 June 2008: See The official way to change MSCRM ports for an official way to do this. Update 12 March 2008:
The discovery service is a web service which gives back the real URL to the web services in MSCRM, so if you changed IIS it still gives back the old ones. There is also a bug in the RTM of MSCRM 4.0 which causes it to use the machine name instead of the host header after upgrades. So you go to http:///mscrmservices/2007/crmservice.asmx which doesn't exist since yourhost headers should have it as http:///mscrmservices/2007/crmservice.asmx
You can pick this up using fiddler on the email server or desktop machine when trying to configure the email router or outlook client respectively. So I went though this with Microsoft PSS and they came back with a SQL command you can run to fix this.
NOTE: As this is a DB change it is unsupported. If you are a little worried about the impact do backups then try it. If you are very worried contact PSS directly for help.
Example, if your server is called: myserver and runs on port 50000
Once done do an IISReset and restart the Async service and everything should start to work fine! As I said before this came from PSS (in particular Justin Thorp)and I would really like to thank him for the hard workand great responses I got on it.
- An easier way exists to do this now. See Workflow doesn't work, Imports never happen, emails don't flow and Outlook clients cannot connect - Reloaded
- Another issue causing the same problems has been found and solved. See: Request IP Address has different address family from network address.
The discovery service is a web service which gives back the real URL to the web services in MSCRM, so if you changed IIS it still gives back the old ones. There is also a bug in the RTM of MSCRM 4.0 which causes it to use the machine name instead of the host header after upgrades. So you go to http://
You can pick this up using fiddler on the email server or desktop machine when trying to configure the email router or outlook client respectively. So I went though this with Microsoft PSS and they came back with a SQL command you can run to fix this.
NOTE: As this is a DB change it is unsupported. If you are a little worried about the impact do backups then try it. If you are very worried contact PSS directly for help.
1.USE MSCRM_CONFIG2.Update DeploymentProperties SET NVarCharColumn = ':' WHERE ColumnName='AsyncSdkRootDomain'3.Update DeploymentProperties SET NvarCharColumn = ':' WHERE ColumnName ='ADSdkRootDomain'4.Update DeploymentProperties SET NvarCharColumn = ':' WHERE ColumnName ='ADWebApplicationRootDomain'Example, if your server is called: myserver and runs on port 50000
1.USE MSCRM_CONFIG2.Update DeploymentProperties SET NVarCharColumn = 'myserver:50000' WHERE ColumnName='AsyncSdkRootDomain'3.Update DeploymentProperties SET NvarCharColumn = 'myserver:50000' WHERE ColumnName ='ADSdkRootDomain'4.Update DeploymentProperties SET NvarCharColumn = 'myserver:50000' WHERE ColumnName ='ADWebApplicationRootDomain'Once done do an IISReset and restart the Async service and everything should start to work fine! As I said before this came from PSS (in particular Justin Thorp)and I would really like to thank him for the hard workand great responses I got on it.
Subscribe to:
Posts (Atom)
Posts
